So, that vast IT disaster you may have caused? Come in, sit down I have a little sideline in interrogating IT professionals who are suspected of doing bad things. Sometimes it is quite hard to objectively tell the difference between incompetence and malice. In fact it is rare that either are the root cause of the worst screw-ups. The most dangerous techie in your firm is not the disaffected …
Oppressive, obsessive, obnoxious overachieving supervisors, managers and vice presidents who have reached the very top of their Peter Principle position. They can't let the person work by constantly probing and asking/demanding the work be done in the shortest amount of time with the least resources.
Sounds like SOP to me.
>Sometimes it is quite hard to objectively tell the difference between incompetence and malice
It was only after I'd quit my job and seen the company go down the pan that I realized it was incompetence rather than malice.
..so incompetent, that the MD (who I'd though was being malicious) when sacked for his incompetence found out, he tried to email himself over 3GB of sensitive company data using the company's email system
..so incompetent that competence wasn't part of the MD's job spec, so he managed to sue successfully for unfair dismissal.
AC to protect the guilty.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
