You're not a senior engineer until you've worked on a legacy project (2023)
1–10 of 431 posts
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#2[deleted]
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#3Every project either fails or turns into a legacy project.
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#4And I would add, you are not an "expert" until you had to reverse engineer a program who's source disappeared a decade or more ago :)
But an interesting article for modern times.
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#5Only a little senior, if you're still working and not sitting in meetings all day - rungs remain
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#6Is there a significant amount of people not working on code that already exists? That's like the total opposite of my experience
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#7(2023)
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#8I once had a manager that was fond of saying:
> Experience is what you get when you don’t have any.
The only better experience than working on a legacy codebase is working on a greenfield project long enough to watch it become legacy and see the good and bad consequences of past decisions.
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#9By this logic I've been a senior engineer since I started working!
Re: You're not a senior engineer until you've worked on a legacy project (2023)
#10And I would add, you are not an "expert" until you had to reverse engineer a program who's source disappeared a decade or more ago :) But an interesting article for modern times.
I had to do this once and, while I do recommend the experience for professional growth, it was not fun for the most part!