EMA Research Blog: Navigating IT and Security Horizons

IT administrators love to write scripts – at least, the most talented ones do. Scripting provides a powerful platform to automate simple and repeatable tasks. However, like with most powerful tools, there is an overwhelming temptation for scripting to be overused. When faced with a project deadline, a high-pressure failure event, or even just the need to simplify day-to-day events, administrators can unintentionally create scripts that are so complex they actually put the business at risk. I must confess that during my 2 decades-long tenure as an IT administrator and engineer, I’ve written a lot of scripts…a LOT of scripts…and learned a lot of important lessons. Scripting was never intended to replace application programming. Its purpose is to provide a quick and easy resource for performing simple and repeatable tasks. It is not uncommon, however, for scripts to start simple but balloon over time into complex code that is virtually unintelligible even to its author.

IT operations managers are cringing all around the world – desperately trying to avoid those inevitable words from their executive management: “You need to support enterprise mobility.” Their concerns are understandable. After all, IT administrators are already overtaxed with supporting desktop, server, application, and infrastructure management requirements. Asking them to layer a whole new management discipline on top of that can be a daunting prospect. IT managers who find themselves in this predicament often recognize it as an opportunity to practice the fine art of procrastination. Particularly skilled procrastinators will employ one or more of the following excuses: