4

Oh, here's an environment variable that needs to be set in order to work, not mentioned at all in the documentation, only found when your CI/CD fails, blah blah blah i'm an ignorant human who doesn't give a shit enough or have enough pride in my job to write proper documentation

meanwhile managers and "product types" - we don't care about documentation, just being faster and that newest AI blockchain chatbot that we need now even though we don't understand the first damn thing about it, slop slop barf barf

Source, not a small at all org: it's the docker orb: https://circleci.com/developer/...

You need to set the docker password as an environment variable, its not just an amazing 3 step magic wand as the 'steps' suggest

yawn

but you know what? waste my time, as well as all the other developers down the road, that's just how it is these days you know

Comments
  • 0
    Environment variables have been invented by the devils to annoy users and devs. Explicit configuration in files or command call arguments are the right way.
  • 2
    @Oktokolo yes and no.

    Some things must be environment variables...

    What truly pisses me off is when the environment variables are undocumented - making it necessary to e.g. digging through source shell code that looks like puked out noodle soup.

    Or even worse... Literally the worst... The environment variables aren't conformant to bash / shell rules.

    E.g. bla=$`xy works (fails in bash)… but bla='$`xy' (which works in bash) isn't possible as the quotes are interpreted - so the final string inside the non bash program is '$`xy' and not $`xy ...

    Such frivolous heretic acts deserve divine punishment...
Add Comment