"Legacy" is a very loaded term -- generally used in a derogatory way. There is an old engineering truism: "if it ain't broke, don't fix it" When Lindbergh fle

"Legacy" is a very loaded term -- generally used in a derogatory way. There is an old engineering truism: "if it ain't broke, don't fix it" When Lindbergh flew across the Atlantic in the Spirit of St. Louis, the Wright Aviation Company which made the engine for his plane, wanted to do its best to make sure he made it. They carefully built and checked the engine and hand delivered it with a note: "don't monkey with it" (or words to that effect). Lindbergh was a careful guy and he didn't. Businesses and developers need to distinguish between warranted or needed changes to working systems (software or otherwise) and ego trips. Real systems are built in limited time, with limited resources, even if they have a multi-billion dollar budget. Invariably there are things someone can make an issue about even in a system with a perfect performance record. Why did you hard code 3.14159267 instead of having a general variable for PI initialized to 3.14159267, and by the way why do you have only 8 decimal places -- wouldn't 16 be better? It is an ego trip and it is the ancient territorial imperative, marking your territory by deprecating the previous person or team -- or a colleague. Joel Spolsky wrote a famous and widely ignored blog post on this sort of thing: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-... Take a deep breath and ask yourself: is this something we really need to do or am I (are we) showing off/putting someone down/behaving like a spoiled adolescent?