The Software They Were Afraid to Touch

he paper company had been in business for seventy five years before anyone said the quiet part to me.

"We are scared to touch it."

They were talking about their own software. The application that ran a meaningful slice of their business, the thing their people logged into every morning, and nobody on their team wanted to open the hood. Not because they were not smart. Because the last person who truly understood it had moved on, and the framework it was built on had been dead for years.

That is the moment I want to talk about today, because it is far more common than anyone admits.

Here is what a dead framework actually means, in plain terms. Their app was built on AngularJS, the original version of Angular from the early 2010s. Google officially ended support for it on December 31, 2021 (https://www.infoq.com/news/2022/01/angularjs-lts-end/). No more updates. No more security patches. The repository archived and frozen (https://sdtimes.com/softwaredev/angularjs-long-term-support-is-officially-discontinued/). The framework still runs, which is exactly the trap. It works right up until the day it does not.

And the risks are not theoretical. Security researchers have documented that applications still running on AngularJS are exposed to unpatched vulnerabilities, including cross site scripting weaknesses that were baked into the framework and will never be fixed now that nobody is maintaining it (https://www.herodevs.com/blog-posts/post-mortem-on-angularjs-three-years-after-end-of-life). Every month you sit on it, the exposure quietly grows.

So how does a seventy five year old company end up here? The same way everyone does. The software worked. For years it worked beautifully. Success is what got them here. They built something, it did its job, and the business moved on to selling paper. Nobody schedules a modernization project when the thing is still running. You only feel it when a browser update breaks a screen, or you try to hire a developer and discover the talent pool for a dead framework has evaporated, or your security team flags the whole thing red.

When our team at Cause of a Kind got in there, we did not just port the old thing over and call it modern. We rebuilt it on Angular 19, the current generation of the framework, which is a genuinely different animal from where they started. Then we did the parts nobody sees but everybody feels. We put in continuous integration and continuous delivery, so a change could travel from a developer's hands to production safely instead of through a white knuckle manual deploy. We moved the infrastructure to the cloud. And we wrote a full test suite, so the software could tell us the moment something broke instead of a customer telling them.

Here is the proof, and it is not a number on a slide. It is a feeling.

The team stopped being afraid of their own software.

A change that used to cost a week of dread now takes an afternoon. A deploy that used to happen at midnight with everyone holding their breath now happens in daylight, tested and reversible. The thing that sat on their books as a liability became a foundation they could actually build on again. That is what modernization really buys you. Not a shinier screen. Permission to move.

Here is the wisdom I would leave you with, whether your stack is ancient or brand new.

Legacy is not really a technology problem. It is a courage problem dressed up as a budget line. Software does not decay because the code rots in the dark. It decays because touching it starts to feel risky, so people stop touching it, so knowledge walks out the door, so it feels even riskier, and that spiral tightens quietly for years. The framework going out of support is just the moment the bill finally comes due.

The companies that handle this well are not the ones with the newest tools. They are the ones who treat their software like a living thing that needs tending, not a one time purchase that should last forever. Seventy five years in business taught this company how to maintain machines, relationships, and a brand. The software simply needed to be added to that list.

If there is an application inside your business that your own people tiptoe around, the one everyone quietly hopes keeps working so nobody has to look at it too closely, you already know which one it is.

You have known for a while.

The good news is that the fear is the real problem, and the fear is fixable.