26 ms·
You represent the other extreme with your comment. Very few software projects have more than two or three years of "experience fertility," for the kind of exper
by sidlls 10y ago
You represent the other extreme with your comment. Very few software projects have more than two or three years of "experience fertility," for the kind of experience you mean. There's a difference between someone who can't even last a year to get a project from prototype to some semblance of maturity and someone who wants to move on after one to two years when a project reaches the point at which maintenance overtakes new development.
What's the difference between somebody who works on four different projects over 8 years for company X and somebody who works on four different projects for four different companies over the same period, in this context?
- jimmywanger 10y agoNothing different between working at the same company for different projects, and working at different companies. Maintenance work is easy, less time consuming, and frankly mostly requires less effort. If you fall into that trap, and end up maintaining a large system that is slowly becoming obsolete, you're not building up more skills. A lot of older workers (and I am one of them) end up doing that cause that's the easy path, the one requiring no effort at all. And that leads you to becoming unemployable.