Good news stories courtesy of Jess Craven. Even in these troubled times, there are things to celebrate.

#GoodNews #ChopWoodCarryWater #USPol #Progress #WorldNews #HappySunday

https://open.substack.com/pub/chopwoodcarrywaterdailyactions/p/extra-extra-83?selection=17530af9-f8f0-4ec7-ab0a-d86709ac5cda&r=1fzzx&utm_medium=ios

I am doing this big'ish refactor of environment variables for a repo where they are, and not to understate this, A!FUCK!ING!MESS! in all sorts of multiple declarations, people just not understanding how env vars work at all, and failing closed on really bad defaults. None of the variables are being validated, but I won't get crazy about that except for the true/false ones that need to be atoms.

The fucked up thing is just how much entropy is present in just this simple set of 3-4 files. The ownership is absent, so there is no care for the code. "Code is Craft" isn't applicable here, because nobody is given the opportunity to truly own their craft. I'm sure I'm not in the minority.

But anyway what I'd LOVE to do is iterate on sections of these six dozen env vars in different sections and push the changes quickly and know I'm on the right track. But our deploy process here is *so broken* and takes *so long* and would undoubtedly *hit a blocker* because someone *else* is having a problem with the deploy pipeline. So I am stuck doing what I hate, which is building a huge PR. Hopefully though it will "just work" and the configuration settings will be transparent. That's the goal. That will not happen until it fails a few times.

Nevertheless, we (as a team) don't put release timing as a constraint on ourselves, so we are abused by it when it fails. Like my big ugly PR will do.

#SRE #GlueWork #ChopWoodCarryWater #CarryOn #DevOps