Eli5 article review series: The end of one-time software modernization projects

Care and feeding of software

Source: Youtube & Frankwiles

Abstract. The term modernization is often used as a convenient shorthand in the tech industry for "fixing old stuff". However, according to Sam Corcos, the very concept of modernization is built on a fundamental misunderstanding of what software actually is. In a recent episode of the Modern Wisdom podcast, Corcos argued that treating software as a one-time project is a recipe for failure.

Review and insights. The core of the issue lies in the analogy we use for software development. When modernizing software and exploring AI, we found the following core hurdles with the "big bang" modernization vision:

The house vs. puppy analogy: Most people think of building software like building a house, where all the work goes upfront with a trickle of maintenance. Software is actually like getting a puppy; a puppy cannot simply go unfed for a year and still be expected to survive.

The dead puppy: When companies treat modernization as a "one and done" investment, they are essentially buying a new puppy but forgetting to feed it. This leads to the same "dead puppy" result, just rewritten in a newer language like Rust or deployed on a serverless stack.

Incurred debt: If updates happen only sporadically, a massive amount of time goes into simply working down technical debt before new feature development can even begin.

Brittle foundations: Developing on an outdated stack, like end-of-life PHP, means building on a foundation that hasn't seen security support in a decade.

Lost momentum: By the time a major modernization is finished, the landscape has often shifted again, leaving the "new" system already falling behind.

Sam Corcos highlights that the software development process is misunderstood when viewed as a one-time modernization project. Software is more like a puppy than a house. Without regular "care and feeding," the result is still a dead puppy, regardless of the technology stack used. True success comes from viewing software as an evolving, living system.

Full video episode: Care and feeding of software. The end of one-time software modernization projects

The first step to start the modernization journey

Software modernization and architectural rebuilds lie at the heart of Eli5. We solve complexity to deliver direct business value by focusing on pragmatic, cloud-native transitions.

Before deciding whether to wrap the legacy system, buy a new SaaS product, or use AI to build custom tools, total visibility into the current tech landscape is essential.

Interested in booking a free brainstorm to discuss the legacy stack? It is the essential first step to turning technical debt into a scalable, modular future.