4 ms·
On legacy code and bug fixes: “Who wrote this s**t, asked the CTO“
- jgrahamc 4y agoRelated: https://blog.jgc.org/2013/07/your-test-suite-is-trying-to-tell-you.html https://blog.jgc.org/2013/07/your-test-suite-is-trying-to-te...
- lauluz 4y agosome things never change?
- thadt 4y agoYep - I've had exactly this experience. In the past I had skunkworks'd a program which became a primary diagnostic tools at the company. It was maintained in an ad-hoc manner and a number of people worked on it over time. A few years later, I was adding a feature and something just wasn't working the way I thought it should. Tracking it down to some lower level networking code, I saw something that was just obviously crazy. Feeling real anger over how some inexperienced engineer had violated my codebase with their incompetence, I pulled up git blame to figure out who was about to get an earful. And there it was: Me - from 7 years earlier. I'd like to think this happens to most of us that are around more than a few years.