3 ms·

Great point. I actually don't think the one has valuable experience until one spent 2+ years on the same project. All bigger projects get more chaotic and comp

• sidlls 9y ago
  But once somebody has done that once, it's unlikely that additional years will contribute to experience: there's a steep drop off in the marginal experience gained for additional time spent. That's why I wrote what I did: longer than a year or two on the same project in the same capacity is a negative indicator. It's not a deal-breaker, especially if it's just a small fraction of the employment history. If it represents the majority of the developer's history, then I expect to see significant expansion of his role as time progresses. Otherwise he's just doing the "same experience, N years over" trick, just on the other extreme end from the guy who never lasts longer than a year or so to see a project from initial development through maturity and maintenance.
  • majkinetor 9y ago
    'Only once' can't be true. Its like saying that your first long term project will be ideal in providing every type of experience. That is impossible. IMO, you need to have long standing projects all the time, its a domain on its own. I agree with you that it may mean staling for some people, but no generalization is possible.