3 ms·
Some (me) would argue that tenure should not be considered when deciding a developer's skill.
by alexbanks 10y ago
Some (me) would argue that tenure should not be considered when deciding a developer's skill.
- collyw 10y agoFor certain types of problem that may work well, but for me, learning from my mistakes has been where I learned a lot.
- alexbanks 10y agoTotally, but learning from your mistakes is not necessarily tied to years at a desk. edit Also, we've all met that dev that just "gets it" and can be extremely productive regardless of time at a job/company/project. That dev also "got it" when they were pretty new to the industry.
- StevePerkins 10y agoI think that the number of different companies you've worked for (and the diversity in how they operate) is more important than the raw number of years you've worked. Also, how your role has grown or varied from job to job. Rookies worry too much about "job hopping". I can't count the number of people I've interviewed who had "10 years experience"... but really they just had "the same year 10 times".
- alexbanks 10y agoMore jobs = more diversity = more experience, no? Both models are flawed I think, as 10 jobs in 10 years brings a ton of understanding of the overarching principles of working as a dev, but has a total lack of long-term team success. 2 jobs in 10 years brings an understanding of that long-term team success but a relatively small window into dev jobs as a whole.
- deleted 10y ago[deleted]