The fundamental problem with NODE_ENV stems from developers combining optimizations and software behavior with the environment their software is running on.

I'd advise against using NODE_ENV values to branch.

.env.production, .env.development, .env.test (depending on value of NODE_ENV)

This is the Git repo of the Docker "Official Image" for postgres (not to be confused with any official postgres image provided by postgres upstream).

I think you linguists worry too much. It's a simple enough formation using a very common prefix, and while it is not clear whether "I disprefer" means "I do not prefer" or "I prefer something other than" or "I prefer the opposite of" or "I stop preferring", either it'll settle down to one meaning or it'll carry a range. So what? This is the first time I've heard the word but I don't find it particularly puzzling.

John: But that's exactly what I did! Dis- + prefer should theoretically mean "don't prefer" or "unprefer". So what does that mean? You're neutral? I understand the meaning now from the comments. But I don't think the meaning is clear from the components. Just to check my understanding of dis-, I checked a few online dictionaries, and roughly speaking… dis- = lack of, not, apart, away, undo, remove The reason I was confused was that to me, dis- simply neutralises a word. It multiplies the meaning by zero, yielding zero. It's not like anti-, which multiplies by minus one, changing the sign and changing the meaning to the opposite. If you said anti-prefer, I'd have a better idea of what the word meant.

less secure sign-in technology

Shareable Code

Using --ours did what I was after, just discarding the incoming cherry picked file. @Juan you're totally right about those warning messages needing to say what they did't do, not just why they didn't do it. And a bit more explanation that the ambiguity from the conflict needs to be resolved (by using --ours, etc) would be super helpful to this error message.

I guess the interaction between the "false" state and the current runtime default is what has me confused. I see "true" and "false" here more like "on" and "off", and if frozen-string-literal is off, to me that means it does nothing at all and whatever defaults are in place take effect.

with a low level understanding of computing and tech

Include one or both of these headers in your messages:

But this sounds like spreading fear and doubt when the Ruby parser has no such concepts :) {} always binds tightly to the call right next to it. This block {} will never go to using, unless it's rewritten as do ... end.

Filter gives me the impression of inclusion... so if I filter by fruits, I expect to see apples, oranges, and bananas. Instead, this is more like filter out fruits... remove all the fruits, and you're left with the rest. Filter in/out are both viable. One means to include everything that matches a condition, and the other is to exclude everything that does not match a condition. And I don't think we can have just one.

I had not thought about whether dropping means "defined but empty" or "not present at all"

  high school kids vs. high-school kids (school kids on pot, or kids in high school)   one armed bandit vs. one-armed bandit (an armed bandit alone, or a bandit with one arm)   criminal law professors vs. criminal-law professors   small animal veterinarian vs. small-animal veterinarian   old boat dealer vs. old-boat dealer   bad weather report vs. bad-weather report   big business owner vs. big-business owner

doesn't know if .env is a hidden file with no extension or a *.env without a filename.

"It's difficult because we can't tell people exactly what's allowed and not allowed," said Chris Castelli, a manager for the Department of State Lands. "It's even tougher for law enforcement that gets called out to very heated disputes and doesn't have strict laws they can apply." 

ambiguous and invisible Unicode characters

In everyday usage, MST is often referred to as Mountain Time (MT) or the Mountain Time Zone. This can add a bit of confusion as the term Mountain Time does not differentiate between standard time and Daylight Saving Time, so Mountain Time switches between MST and MDT in areas that use DST during part of the year.

Sass currently treats / as a division operation in some contexts and a separator in others. This makes it difficult for Sass users to tell what any given / will mean, and makes it hard to work with new CSS features that use / as a separator.

Can you provide details of what you mean by "not working as expected"?

The specimen copies are made from.

The terms autonym and xenonym also had different applications,[3] thus leaving endonym and exonym as the preferred forms.

but it only worked for me when placed above that conditional

        if (opts.credentials !== 'omit') {
            uses_credentials = true;
        }

It has two very different meanings, that you would have to distinguish by context. One meaning is just expressing that we have limitations. If you don't know something, that's just tough, you don't know it and you have to live with that. You don't have information if you don't have that information. The other meaning is that not only are there gaps in our knowledge, but often we don't even know what the gaps in our knowledge are. I don't know how to speak Finnish. That's a gap in my knowledge that I know about. I know that I don't know how to speak Finnish. But there are gaps in my knowledge that I'm not even aware of. That's where you can say "You don't know what you don't know" meaning that you don't even know what knowledge you are missing.

that can be played by up to 10 local players - turnwise.

However, some users didn’t know that they could interact with and click on the text field. It looked like an empty box. The line affordance under the old text fields was not clear to some users. The line was confused with a divider.

The label and input were confused with body text, especially in dense compositions.

<aside> is not appropriate if the side note is "a parenthetical". The W3C gives no examples of what it means.

It might be possible to fix it in Capybara, but I'm afraid that we'd just add more unexpected, ambiguous behaviour (which key should have been pressed, backspace, space?).

It consists of two relations; the first one being exemplified in "An X is a Y" (simple hyponymy) while the second relation is "An X is a kind/type of Y". The second relation is said to be more discriminating and can be classified more specifically under the concept of taxonomy.

place

Every woman talked to a student. This has two interpretations. Under one reading, every woman talked to the same student (the class president, for example), and here the noun phrase a student is specific. Under the second reading, various students were talked to. In this case, a student is non-specific.

those aspects of a linguistic unit, such as a morpheme, word, or sentence,

Anyway, sorry for the short novel. But that's the danger of pithy one-liners: assumed context for the poster can be entirely lost in translation.

So if you get a number of 130, there's an ambiguity in that you don't know whether the process dies of a signal 2 or just did an exit(130).

I meant to say after I published Reform I changed jobs (unrelated to Reform) and in the new project, we don't use Reform, yet

A button that simply said “Confirm” wouldn’t necessarily make it immediately clear about what the reader’s action means.

There’s only one hard thing in Computer Science: human communication. The most complex part of cache invalidation is figuring out what the heck people mean with the word cache. Once you get that sorted out, the rest is not that complicated; the tools are out there, and they’re pretty good.

Cache and caching are some of the most ambiguous words in the IT world, and that’s because we can have multiple types of caching working in parallel and affecting content independently.

I disagree, but I can't downvote it, because it is an important POV.

If you try to render content along with a non-content status code (100-199, 204, 205, or 304), it will be dropped from the response.

if the value given in value is contained in the array that is the value for the field for the form

I think it is still problematic since many people in the software industry use and understand "dependency" to mean the thing on which something depends (as indicated by this and other answers). So saying "being a dependency" indicates to those people the thing on which something depends, which is the opposite of the way I think of it (and what it means according to the dictionary).

Optionality — Degrees of Freedom over Forecasting

Could you avoid the word "instance"? It is confusing to me with an instance of a class. How about "all occurrences"?

When you hear there's something called "template strings" coming to JavaScript, it's natural to assume it's a built-in template library, like Mustache. It isn't. It's mainly just string interpolation and multiline strings for JS. I think this is going to be a common misconception for a while, though.

Disqus does not allow that user can use free licenses for their comments. It is not clear who has ownership of the comments.

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. They are contrasted with functional requirements that define specific behavior or functions

Perhaps "Mask this variable" would be better language to use, as "protect this variable" may be easily misinterpreted.

PRA

ignore shared content across pages

quantum blockchain

must keep records of any processing activities that are "not occasional".Does anyone have a clearer definition as to what not occasional processing might be under this definition?

While there are no legal precedents to spell out specifically what the actual terms mean, it can be interpreted from the testimony of people like Professor Mark Lemley from Stanford University, in front of the United States Senate Committee on the Judiciary that the individual terms are defined as follows

monitor such users’ behavior taking place in the EU.

gets awkward with wider usage

Repeats

As you indicate, it will be misunderstood in some quarters, which might be a good reason for avoiding it.

and more

warm welcome

applicable to select eBooks, digital music, videos, and apps

Had a read through a few of the linked articles above... Wow. Messy, headache inducing stuff, and still so much vagueness.

European Union, USA

If you have confidential or private content that you don't want to appear in Google Search results, the simplest and most effective way to block private URLs from appearing is to store them in a password-protected directory on your site server. Googlebot and all other web crawlers are unable to access content in password-protected directories.

The foundation of good style is correctness of language, which falls under five heads. (1) First, the proper use of connecting words, and the arrangement of them in the natural sequence which some of them require. For instance, the connective "men" (e.g. ego men) requires the correlative "de" (e.g. o de). The answering word must be brought in before the first has been forgotten, and not be widely separated from it; nor, except in the few cases where this is appropriate, is another connective to be introduced before the one required. Consider the sentence, "But as soon as he told me (for Cleon had come begging and praying), took them along and set out." In this sentence many connecting words are inserted in front of the one required to complete the sense; and if there is a long interval before "set out," the result is obscurity. One merit, then, of good style lies in the right use of connecting words. (2) The second lies in calling things by their own special names and not by vague general ones. (3) The third is to avoid ambiguities; unless, indeed, you definitely desire to be ambiguous, as those do who have nothing to say but are pretending to mean something.

Words of ambiguous meaning are chiefly useful to enable the sophist to mislead his hearers.