3 ms·
> fulfilling to tackle a new project and a new tech stack every 18 months. That's not what I mean by 1 year of experience 10 times. That's 1 year of experienc
by cratermoon 4y ago
> fulfilling to tackle a new project and a new tech stack every 18 months.
That's not what I mean by 1 year of experience 10 times. That's 1 year of experience with specific technologies, which nobody except recruiters and HR people looking to mindless fill out a job description care about.
By 1 year of experience 10 times, I mean working in the same ecosystem, doing coding but never really going beyond that. It seems like there's always someone in every position I've had. They have a long resume, but look at their code or their overall development practices and you'd think it came from a junior coder new to the industry.
Establishing yourself through learning a new tech stack every so often is fine – as long as you demonstrate that your skills as a developer have grown. Going from not owning any specific area of the code, helping in other people’s areas, fixing bugs, making small modifications, and implementing very small features to owning an entire product, in all aspects of the development process, providing technical direction to others, doing design and making architectural-level decisions is establishing yourself.
- urthor 4y agoOh good, that makes perfect sense. I've just found the idea of "1 year of experience repeated 10 times" at a dissonance with an industry very much oriented around staffing individual projects. I agree, as long as you're building those skills of ownership, that's progression. I've just had many say you need to stay at a place 5 years to do that, which is crazy to me.
- cratermoon 4y agoOh no, it's definitely ok to move around and change technologies. In fact, it's probably an advantage to know 1-2 really deeply but have familiarity with more.