Don't Let Your Code Become Legacy
15:30 - 16:00
Some projects may last for decades. And some of them are still heavily maintained. Is any of the initial code still in use? Is that code Legacy? How do we add functionalities to such an old code?
I worked for about 14 years on the very same project, so I got to be the "expert" where new team members found answers. But I don't think we really need that kind of an expert in a long maintained project. We just have to write our code right, and most importantly, we have to also maintain the code, not just the project, to make that role disappear. Code maintenance is just some good refactoring, wherever it is needed. The boy scouts rule is: “Always leave the campground cleaner than you found it”, and it applies very well to the developers too. Our campground (the code) should be always cleaner after we touch it.
