I really like that a lot of people in construction work just dont take anyones bullshit. If someone fucks up, it gets fixed. Sometimes with a lot of cussing.
Meanwhile as a programmer if you call out anyone or anything for doing something wrong, you get immediate backlash cause of it. Its a lot like that you are the problem for calling it out and not the one who caused the problem in the first place.

I think you're romanticizing it a bit.

@N00bPancakes Yea, that toxic behavior tends to be the exception, not the rule. At least, I hope so.

Thats novel.

I'm Not supposed to curse the DevOps idiot that deleted all the client live system data? You sure?

Oh for fuck sake.

Not my experience. If you call BS on something, you will most likely be the one fixing it.

(But only if it's deemed important enough to be fixed at all ofc)

Well in my experience, If you so much as dare call BS on something it immediately gets the sacred status of "tech dept" and you will be the one everyone calls "grumpy" or "perfectionist" from now on...

I just lost a promotion because of this shit... they said I demoralize my coworkers with negative thinking even tho they agreed that the stuff I bring up are legit problems but I should work on the way I say it and think of a way that wouldnt hurt morale... Wtf does that mean? The problems raised arent even the current teams fault but the legacy codebase and inherited bad workflows and unreasonable deadline.