Projects that require large amounts of code stability do make a large amount of effort to be non-dysfunctional and provide appropriate growth opportunities to team members at all stages of their careers. Engineers are often too expensive to simply burn out and discard.
Some colleges just filter people through too many too large classes, and then reduce the curriculum when people aren't doing well. On top of that, most college students are in their late teens/very early 20s and may need to make changes.
In any case, there are bad college programs and nurturing work places. There is nothing wrong with leaving a bad workplace, but there is also nothing wrong at staying at a great one for many many years.
Projects that require large amounts of code stability do make a large amount of effort to be non-dysfunctional and provide appropriate growth opportunities to team members at all stages of their careers.
Shouldn't all projects have code stability? I can't imagine software instability being a good thing ever.
There is nothing wrong with leaving a bad workplace, but there is also nothing wrong at staying at a great one for many many years.
Absolute agreement on that one. I don't want to change jobs every 6 months-- or even every 5 years. I'm sick of that shit. However, I've observed that a large number of employers treat their employee badly and those deserve no loyalty.
Some colleges just filter people through too many too large classes, and then reduce the curriculum when people aren't doing well. On top of that, most college students are in their late teens/very early 20s and may need to make changes.
In any case, there are bad college programs and nurturing work places. There is nothing wrong with leaving a bad workplace, but there is also nothing wrong at staying at a great one for many many years.