Another example is password complexity rules, we try to use latest recommendations with no forcing of PW change, no requirements beside length - but then there will be customer that will make fuss that we don’t have it as as it is compliance check box to have complex PW.
Skipping code reviews and the poor code that can happen because nobody took a second look - that's more of a problem. Because 6-12 months down the line, there's not a few bugs that need to be fixed. Instead, there's a horrible code base that causes all _future_ development to be a lot slower.
[Budget proposal officer]: "Here is the new cleaning budget"
[CEO]: "looks around the office, the office is clean, why do we need cleaners? much less expensive cleaners"
[Budget proposal officer]: "The cleaners keep the office clean though"
[CEO]: "Nonsense! I read a substack about this, lets get rid of the cleaners"
//Six months later in an ALL hands//
[CEO]: "Look I know that we have had issues, The washing facilities were sub standard, and in some cases people were poisoned by poor hygene. We have insistuted a new mandatory training called `keeping the office clean, you're the first link in the chain` to help keep everyone happy and healthy"