The melting iceberg of legacy code

“Legacy code” is that code in an organisation which has been around for some time, and it bears considering the career issues that it represents.  It can be both an opportunity and a threat to our careers.  On the plus side, legacy code can have the attraction of offering some stability and comfort.  For those of us who hate having to learn a new technology every five minutes, programming in this type of environment can have its advantages: life is more predictable, and most major problems with the code should have been ironed out by now, so the issues that tend to arise are much more predictable and manageable.  Also, if you’re one of the few remaining people around who know how the system works, then you’re probably quite valuable to your company.  However, you should also consider how to deal with possible downsides.  Are your company planning to replace the legacy system at some point?  Are they training you on new technologies? How will you transition to the new systems?  Are you being disadvantaged by working on the old software, while others get to put shiny new skills on their CVs?  If these questions raise issues that apply to you, then consider raising them with your boss, or call us at the IAP office for an informal chat on how to deal with the situation.  The chances are that another member has been through a similar situation and may have some helpful tips.

Martin Doe

Comments are closed.