EA: Prevention is better than cure

Create a vendor selection project & run comparison reports
Click to express your interest in this report
Indication of coverage against your requirements
A subscription is required to activate this feature. Contact us for more info.
Celent have reviewed this profile and believe it to be accurate.
16 September 2010


  • Deeper analysis of why IT Architects prefer rip and replace is in order.

    1. I have ran across developers and architects who have made technology choices solely for personal interests that have caused long term harm to the business. Likewise, I have ran across developers and architects who have incrementally leveraged legacy technology for business competitive advantage. As you are aware, many enterprises are dramatically scaling back their workforce and the developer with the resume that shows the latest hot technologies is more than likely to get a job faster when displaced when compared to his peer that otherwise has legacy skills. In today's marketplace, it is very difficult to encourage a developer to not be selfish especially when their enterprise is scaling back.

    2. I think want else is missing from the conversation is the acknowledgment of different skills being required above and beyond language choice. In the building trades, Architects are really good at designing new systems from scratch, where they may not necessarily be involved with "remodeling" something that already exists. The same challenge exists amongst the IT Architect crowd in that they may know a language and good design but may not have the skill to pull off a large scale "refactoring" effort.