4 ms·

While you can't train experience, the value of experience decreases steeply over time. Sure someone at year 0 has less utility than someone at year 10, but the

While you can't train experience, the value of experience decreases steeply over time. Sure someone at year 0 has less utility than someone at year 10, but the difference may all but disappear when comparing year 5 vs 10. Edit: I started out as a BBS sysop. So you can see which side of the equation I'm on. The value of knowing how to admin door games is practically zero at this point.

synnik 15y ago
This may or may not be true... it is an example of the old statement that I learned in martial arts" There is a vast difference between having 10 years of experience, and having 1 year of experience repeated 10 times. The reason there are often few differences between a 5-year career and a 10-year career is that most people find a niche after a few years, and comfortably sit there. But if you can find someone who spent 10 year actively learning and broadening their skills, never settling in... those extra 5 years are immensely valuable.
aidos 15y ago
I see where you're coming from but when I put myself in that statement it just doesn't work. My now self, with nearer to 10 years experience would tear my 5 year experienced self to pieces on all things technical. I'm doing things now with great efficiency whereas 5 years ago I would probably have made a bit of a mess of them. Though obviously at year 5, if asked, I would have happily told you I knew it all already :)
jfischer 15y ago
I think you can divide (useful) experience into two components: 1) a person's maturity as a programmer / team member, and 2) their level of practical knowledge with a given technology stack or your problem domain. I think that maturity is undervalued in this industry and is a must-have for senior developers. For practical knowledge, it can be extremely helpful to have someone who knows where the bodies are buried in the tech stack you are using. However, if you already have the knowledge on your team, then getting someone who can pick things up quickly might be a better focus.

synnik 15y ago

This may or may not be true... it is an example of the old statement that I learned in martial arts" There is a vast difference between having 10 years of experience, and having 1 year of experience repeated 10 times. The reason there are often few differences between a 5-year career and a 10-year career is that most people find a niche after a few years, and comfortably sit there. But if you can find someone who spent 10 year actively learning and broadening their skills, never settling in... those extra 5 years are immensely valuable.

aidos 15y ago

I see where you're coming from but when I put myself in that statement it just doesn't work. My now self, with nearer to 10 years experience would tear my 5 year experienced self to pieces on all things technical. I'm doing things now with great efficiency whereas 5 years ago I would probably have made a bit of a mess of them. Though obviously at year 5, if asked, I would have happily told you I knew it all already :)

jfischer 15y ago

I think you can divide (useful) experience into two components: 1) a person's maturity as a programmer / team member, and 2) their level of practical knowledge with a given technology stack or your problem domain. I think that maturity is undervalued in this industry and is a must-have for senior developers. For practical knowledge, it can be extremely helpful to have someone who knows where the bodies are buried in the tech stack you are using. However, if you already have the knowledge on your team, then getting someone who can pick things up quickly might be a better focus.