A story about technology debt and how to fight it
Press enter or click to view image in full size
Imagine it’s the year 2002 again. You just got a massive pile of money from angel investors and are about to start a new company. In the time of the digital revolution, when software seems to be the key to success, you decide that you hire 100 developers to start everything off. So you start recruiting. One of your partners knows a thing or two about technology and decides that your core technology should be based on <Java/C/PHP/C++/Python/Pick your poison>. Also, it looks like there are plenty of developers that know the chosen ecosystem on the market. Eventually, you find all the developers, build the teams and start building the software.
Time goes by and hundreds of software components are developed during that time. We are back in 2022 and the company has grown a lot. Everything seems to be going great until a newly recruited developer walks into your office. She is concerned that their team is starting a new project and they are forced to use the same technology you and your friend chose back in 2002. In her opinion there are:
- Newer versions of the language/framework/service available that are more performant and better security-wise
- New languages/frameworks/services that are overall a better fit for the project
- Existing solutions that…