The phrase “legacy code” can have several different interpretations; for the sake of discussion, let’s define it as “code written by someone else, and which you now have to use”. These past couple of weeks I have had the opportunity to work legacy code written by an employee of the company. This opportunity has proven both challenging and rewarding, especially since it forces me to think harder about good programming and software development.
We have all seen it – the file that comes across our inbox, or resides in our Documents folder with a name along the lines of “Important File final_version_some-edits_final-for-real_V2.docx”. As companies and businesses produce more and more knowledge and information, the tasks of trying to keep that information up to date and track where it came from become increasingly complicated.