> New devs almost certainly shouldn't be given maintenance and repair tasks. This would just massively increase churn. Old guys get sick of doing the same old

> New devs almost certainly shouldn't be given maintenance and repair tasks. This would just massively increase churn. Old guys get sick of doing the same old crap especially when seeing the new guys get all the good stuff. So it increases the likelihood that people will just move around a lot more often in order to build that "new stuff". Eventually you'll have lots of companies saturated with "new stuff" that's no longer so new and nobody to maintain it because everybody knows the second you're too old in the company you get saddled with maintenance tasks. > the old guard wants to move on from the problems they created Just because it's old doesn't mean it's a problem. It still has to be maintained though, with higher effort since the technology may be outdated. Even the best designed systems become a chore to maintain when you have to do it for 10 years instead of doing anything new.