System Rewrite in Startups

By definition, a legacy system is a system that is difficult to support regarding software or hardware updates. In startups, systems are termed legacy within 5 or 10 years. This is mainly due to a need for more documentation, incoherent architecture, and development before joining an engineer; any system in the organisation usually becomes a legacy system. The idea floated that writing a new system is always better than understanding the existing one and fixing the issue. This is only the case sometimes. Most of the time, writing new systems optimised for people rather than organisations. It takes work to understand the existing code. It gives less satisfaction to people fixing something than creating. This does not look good on resume as well. I won't recommend developing a new system unless

• the system uses a tech stack that is not in use anywhere in mainstream development or is very costly to maintain
• needs much change in functionality and presently supports very few use cases
• it breaks loose all hell now and then
• My teams have time and are not busy developing anything important