In 2013-2014, I was tracking a strange bug in a legacy accounting software. I was reading the business logic that triggered the bug and it made no sense. I ac

In 2013-2014, I was tracking a strange bug in a legacy accounting software. I was reading the business logic that triggered the bug and it made no sense. I activated the blame view of the code, and I realized most of the code had been written in ~1998 but a couple lines had been updated in ~2007, by someone who probably never even met the original author. Realizing that made it a lot easier to understand the context of the bug and fixing it. There is a lot of value in knowing that two lines of code next to each other have been written decades apart by people that did not coordinate with each other. Never erase that history voluntarily.