Retire legacy systems: reduce burden, improve results
As a junior developer you learn and get quite intimate with many legacy systems. It's almost like a rite of passage, you finish school, interview, get a job and your first project is working on a legacy system the rest of the team hates. Or if you are new on a team you pick up a legacy tool or app that no one else wants to touch. Funny thing is, as you go through the ranks and become more senior you also tend to get more intimate with many legacy systems. Usually they fall into your lap during changes (management or leadership), acquisitions or if you produce results you are guaranteed to be saddled with technology no ones else wants to deal with.
Topic
