[lostcolony]

Oh yes. There is nothing quite like "it cost us money" to suddenly change leaderships' priorities. I've watched as product priorities went from "keep bolting on features" to suddenly "we should rewrite this problematic monolith" when thigns fell over and money was lost.

[yaml-ops-guy]

See that makes sense, perhaps it make too much sense. My last two jobs I fought the same battles of "I discovered x, we really should do something about it because it can have really bad outcomes" and having the concern depri'd and ultimately blow up in all of our faces.

And in both situations even when said thing exploded in a bloody mess I struggled to get the buy in to give the fix the full attention it needed because "we're losing money not having these features" (I mean no, you're not, but ok)

Hence my incredulity but honest curiosity, being an ops guy who over-prepares and tries to keep his leaders as informed and prepared to make a decision as possible, but still feels like he's often left holding the bag is dang exhausting, you know?