Don’t call yourself a senior until you’ve worked on a legacy project.
Everybody hates working on legacy projects, me as well. Working on one, however, helped me get a deeper understanding of the dev process.
Read in full here:
This thread was posted by one of our members via one of our news source trackers.
Beautiful article! The main key takeaway:
“We couldn’t change the project we were assigned to, and these were the cards that we were dealt. What we could change is our attitude towards the legacy project . Instead of feeling resigned, we saw it as a place to ask questions and learn.”
And this gem:
"It taught us how things were done before and why they are done differently now. Instead of just knowing the best practices, we gained first-hand experience with the history behind them. "
Side note: this is why I love DevTalk. There’s no way I would have found this blog without this site 
Here’s your answer to the question on every one’s mind lately - Will AI replace the need for developers? Try working within the constraints of a brownfield project in which context for decisions has long left the building and new requirements insist that no behavior from past years can be changed. But, do a good job in a timely manner. 
