Thanks for sharing the video. I'll also mention that reading Michael C. Feather's 'Working Effectively with Legacy Code' changed my perception of the word 'lega

Thanks for sharing the video. I'll also mention that reading Michael C. Feather's 'Working Effectively with Legacy Code' changed my perception of the word 'legacy' in the context of software. Why do businesses pay all this money to maintain 'legacy' code, when they could just rewrite it in the newest, best tech? 1. Because the 'legacy' software often makes money out of proportion with its cost, either directly or indirectly. 2. Because much of the human understanding that is encoded into the legacy software is gone from the company and would be difficult, expensive, or impossible to recreate. The first point should help you feel better about working on 'old' tech. While a million developers are all cranking out react webapps that nobody will care about in a couple of years, you are working on software that has proven itself valuable to the company over time. The second point could help give you a hint at how to leverage a position maintaining legacy code into something good for you and the company. You are close to some 'secret sauce', and if you can identify and internalize what's valuable there, you become indispensable to the company. I've seen that turn out to be very lucrative for engineers if they play their cards right (a.k.a. learn things that nobody can find with any amount of searching the internet, and turn it into pay).