I disagree that Enterprise is "broken". Enterprise is simply a different set of priorities. It's important to be able to look at software from a business pers

I disagree that Enterprise is "broken". Enterprise is simply a different set of priorities. It's important to be able to look at software from a business perspective (where software is simply a tool to accomplish a task) as well as from a developer/maintainer perspective. For example, I'm currently rewriting a major system that has been in use here for many years. Our estimate right now is the total time for the rewrite will be about 2700 person-hours over the course of about 18 months. Supporting the existing system takes about 10 to 20 hours per month. The existing system uses deprecated libraries, unsupported 3rd party components, monkey patched to hell, tightly coupled and has many issues. We can't even rebuild the entire thing from source code because we have unlicenseable components! But, from a business perspective, the current system has run for many years and is likely to continue running. At 10 to 20 hours per months of support, it would take 15 years to add up to the 2700 hours we're spending in less than 2 years on a rewrite. And a rewrite, like any software, won't be zero-support. In addition to mapping those hours to dollars, they also map to other features in other applications. Every extra hour I spend on this rewrite is a feature or improvement on another application that could have been done, but was deferred. In the end, from the business perspective, the new application and the current one are basically identical: the serve the same business purpose! So why spend the hours on a rewrite? Why not just continue to support the current system. So, as a software person, we hate certain badly broken software that we want to bulldozer and start fresh. But from a business perspective, the only concern is value, cost, and ROI.