No matter what the language is, script writing is labor intensive. Writing a new script means that you likely have spent hours designing, writing, testing, and de-bugging the code, and then testing and de-bugging it a few more times. And once they are written, these scripts have to be maintained and catalogued. In addition to these foreseeable challenges, there are the things you can’t predict; requirements can change and developers may leave, and that means you’re going to have to revise or rewrite older scripts.
What does it mean for an IT organization to adapt to change? In today’s high-tech world, even the notion of adaptation itself is changing. How can anyone keep up?
IT organizations are being pushed like never before. Timelines are shrinking, projects are multiplying, and tasks are becoming more complex. Computing resources have shifted from expensive and scarce to highly available and affordable—a mixed blessing, since plentiful resources simply allow business expectations to be that much higher.
We had the opportunity to talk with many PowerCenter users at Informatica World in Las Vegas in May and they shared a lot of information about their IT Automation requirements, at the application and enterprise level, and how it could be improved. Application vendors, as we have previously addressed in our earlier posting, focus their resources (money and time) in developing the core capabilities of their products rather than enhancing their solutions with a robust automation system necessary to address today’s business and operational requirements.