As IT professionals, we all reach a certain point in our IT career where we realize that some of our everyday tasks are done the same way year after year without anyone questioning why it’s done that way.
Despite the constant change and improvement in technology, some things just get done the same ineffective way without any real thought behind it because “that’s the way it’s always been done.”
A typical example: patching
Month in, month out, a day comes along that is dedicated to patching.
Patching may be more automated than before because you no longer need to log into each system to patch and reboot tediously. It’s a step forward, but the patching process remains the same.
Patching is disruptive, slow, error-prone, and rarely fast enough to keep up with new vulnerabilities. Why disruptive? We all know that every time a maintenance window comes along, Bob from accounting will remind everyone how “the company’s IT is going to mess up our week.”
He’s right, of course, because performing patching the way it’s always done impacts a business by completely stopping operations or slowing everything down. Companies and their stakeholders don’t like it, and it means that patching reinforces the idea of IT as a money sink inside an organization rather than a driver of business value.
images from Hacker News