Comments on: The Right Attitude to Deal with Legacy Code

By: Guillaume Roguez

Guillaume Roguez — Thu, 12 Oct 2017 01:35:00 +0000

Thank to mention this part of the developer life.
We’re human after all. We tend to mix technical issues with social/psychological problems… specially when we don’t have any pre-knownledge of who did this.
Sometime is a way of exulting some frustation.

PS: I don’t wait 6 months to complain about my code, a night could be enough 😀

By: Nico Bako

Nico Bako — Tue, 10 Oct 2017 18:16:00 +0000

I’m surprised this article only has one comment. Perhaps it is because working with legacy code is so devastatingly demoralizing that most people would rather not even think about it.

Thank you for the article. I have only been working as a C++ software developer for 5 months. I have been tasked with maintaining and updating a 3D modeling program. It was written by a developer who had a Fortran background. As a result, the code is not expressive, it does not use OOP techniques, and is extremely difficult to understand…

However, I must admit that IT WORKS!!! It is pretty fast, and has relatively few bugs. And plus, I probably couldn’t do any better…

By: tuskcode

tuskcode — Sun, 25 Jun 2017 02:09:00 +0000

This is great article. Some colleagues and I had to look back at a couple of old code bases in the last fortnight. The dialogue was fairly colourful, to say the least.. In the same vein as this article, it was good to get back to newer code bases and appreciate how much things have improved!