InformationWeek is part of the Informa Tech Division of Informa PLC
This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
The State of Cloud Computing - Fall 2020
Download this report to compare how cloud usage and spending patterns have changed in 2020, and how respondents think they'll evolve over the next two years.
2021 Top Enterprise IT TrendsWe've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you.
Tweet This
User Rank: Apprentice
3/6/2014 | 5:22:08 PM
You points are very valid and have been in play for years though many firms have failed to realize the benefits of such actions. I have spent over 20 years adjusting automated tasks to reduce down time and improve overall efficiency of the entire development cycle - requirements, design, coding, QA, deployment, production, maintenance and bug fixes.
Many organizations have low hanging fruit where tasks can be used to:
1. Reduce delays in getting senior management involved in determining when clients could or should be notified.
2. Prevent production failures or automatically scheduling review of non critical processes.
3. Streamline support through publication of recovery steps in alerts.
4. Provide Independent analysis and pre QA review of vendor updates.
5. Create Pattern recognition of development schedule conflicts and coding failures.
6. Do Maintenance / Oil change work that routinely targets poor code.
7. Perform Analysis of systems business rules with the ability to see complex failure points.
I don't think that it is so much a "convert or be redundant" situation for programmers since some of these trends take many years to evolve and are full of failures "lots of silver bullets around", rather I see this as an opportunity for the industry to evolve and in many ways go back to its roots to when quality was paramount and most programmers thought of work as a career and not just a job.
If what you say does come true then I welcome it for maybe we will finally see the end of companies like Yahoo and Google spreading poor coding practices and pathetic customer response practices. Yahoo's recent email disasters would have been laughed at as "Junior Mistakes" only a short time ago ... yet are currently praised by the likes of google as the "Way to develop".
Companies that take on your proposed approach can not only benefit from reduced development costs but much lower maintenance costs, higher customer satisfaction and probably more importantly the subtle benefit of dealing with a company whom you can trust to provide you with a quality product or service.