Telling people who know what they are doing how to do their job often results in bad things happening. Malicious compliance is a thing.
Archive: https://archive.today/UuRZf
From the post:
>Techies are often beset by undeserving and despicable dolts who demand daunting feats of tech support. Which is why each Friday The Register brings you a fresh instalment of On Call – the reader-contributed column in which you share stories of defeating those dunderheads. This week, meet a reader we'll Regomize as "Norman" who is an electrical engineer by trade and during one phase of his career found himself doing a lot of office refit jobs, most of them in the financial district of the City of London.
On that day, @Stupidbird gave zero fucks. He always gives zero fucks, but that day it truly meant something.
When your people say I don’t think that’s a good idea, you stop and find out why.
This actually has happened twice to me. Both times I told "overseer" to go to his office and write me an email ordering me to do this. The first one actually did it and I brought down the system as ordered. Took the entire day to bring it back. I forwarded that email every VP and Manager in the GAL, as well as HR. The second overseer (many years later) stopped and thought for a few minutes and decided to "look into this further" before "we" moved forward. Yeah...it's "we" all of the fucking sudden when this trust fund fuck thinks for a sec and decides his stupid idea really is stupid.
Neither of them had any business being in IT management.
(post is archived)