I know in the grand scheme of things it’s meaningless, this is just one of those things that’s like someone scratching their fingers down a blackboard when I see it day to day.
I know in the grand scheme of things it’s meaningless, this is just one of those things that’s like someone scratching their fingers down a blackboard when I see it day to day.
Tangentially, "Prod" is justified since it's being treated as a proper name, like "Paris", "Roderick", or "Mount Rushmore."
But yes, "PROD" is harder to explain, and I suspect it might be bleed-over from looking at code or config files where it gets capitalized.
I'm trying to train myself out of this nonsense, but some habits die hard.
Not sure if this is a bash hold over to differentiate ENV_VAR vs local reg_var or like an os/global constant naming hold over.
Generally if you call "env" on your cmd line (all of my)/most keys are ENV_VAR capitalized.
Think about book titles. "Exploration of Paris", the important words are capitalized.
I can imagine many people capitalize the environment names without thinking too hard about _why_ they do it.
This is, of course, descriptive typography. Prescriptive typography will vary from style manual to style manual.
Well that's the dictionary definition anyway. In practical terms, I think most people use acronym as a synonym of initialism, at least in the US. This is one of the places where the dictionary definition doesn't match with real world usage.