Usually, when you think of a software engineer, you picture someone quietly typing lines of code, solving bugs, and sipping coffee. But behind that calm screen is often a storm of office policies, manager expectations, and impractical workflows.
For instance, an engineer shared their wild ride with a company policy that sounded good on paper but made zero sense in practice. It demanded every single code change be deployed across all servers within two weeks or get explicit managerial approval. Instead of ignoring the rule, they followed it to the letter, forcing approvals for every update and documenting the chaos. What followed was a masterclass in malicious compliance: one that didn’t just highlight the policy’s flaws, but ultimately forced leadership to scrap it entirely.
