How Not to Be Automated Out of a Job
|
It's becoming more and more difficult for the IT layperson to survive in an industry that is continuously using faster and more advanced technology to automate functions that would have been a person's sole job only a few years ago. What's a job seeker to do in an increasingly commodity-driven IT world? Advice from one industry analyst is to become an expert in automation technologies. Learn a spectrum of systems management technologies and get intimately familiar with cloud technologies. Don't be one cog in large, fast-changing wheel. Be at the center and know what is happening everywhere. Every automation technology needs human oversight and needs to work within a given company's networked system. But more than that, Forrester analyst, James Staten, is telling executives that IT needs to be a whole lot more flexible in its approach to working with the business, and that the perception of most IT departments is that they are in the business of saying no. Staten promotes applying aspects of the agile application development process to IT practices in general to help IT and its workers get in line with flexible business needs, according to a post by Ann All of ITBE who attended the itSMF Fusion conference. All wrote of Staten and his take on automation's perceived affect on jobs:
Staten then discussed how IT departments, especially those involved in infrastructure management, be involved with using cloud services like Amazon's EC2 and Google Apps and keeping things reusable. At issue are business users, and the drive of many technologies toward populist use. Business people will be driving more and more technology strategy based on ease of use and rapid deployment. The cloud and automated applications are only going to assume more of the IT management space. Get busy on them. |
For more IT Careers and Workplace News, check out eWeek Careers

Comments (1)
Actually it's the business units which percieve IS as "being in the business of saying no". IS has the perspective that we must stop our clients from hurting themselves. A large part of the IS role in any organization is Risk Management. So we must sometimes say no, but it's the reasons for saying no that must be understood.
Posted by Jaguru | October 5, 2010 1:02 PM