|
|
|
|
|
by peteradio
1329 days ago
|
|
You are basically saying big work doesn't ever get done in 3-6 months of someone joining a team, or its so remarkably rare that you would rather completely write off the rare case (who sits at the opposite spectrum of what you wish to weed out) than risk hiring a basket case. Mountains don't ever get moved, the problem gets planned properly or it doesn't. Testing takes forever but development along a single trajectory is always fast. |
|
Significant contributions aren’t a settled thing after six months. There always are loose ends to tie, things to reflect upon or unforeseen evolution forcing you to come back.
The issue with people leaving after six months is not that they might not have made a significant contribution in these six months. It’s that they never had to live through the consequences of what they did. It’s not a deal breaker but it’s career limiting because I very much want to hire people who know how to deal with things not going to plan and able to own their work. That’s why experienced people are paid more after all.
I’m equally suspicious of people with ten years of experience who can’t explain to me when something they were working on went wrong and what they did to fix it. It’s nearly impossible to work ten years on major projects and not having something blowing up on you at some point.