Great way to lay out the long-term strategy of a developer career. I'm a big believer in strategic thinking when it comes to career plans.
I want to respond with two points:
First, this is one possible career progression out of many. The starting point in any career plan is to ask yourself what your end goals are -- for example what's your dream job as a developer. Then make a progression plan (maybe like this one, or maybe different) towards that goal. In real life, careers have many more twists and turns, and much more ambiguity in terms of stages and titles.
Second, the article's definition of "coder" is entirely abritrary and I think it's inaccurate.
A better definition of a coder is: "someone who writes code." That's it. It could be an amateur or it could be a pro. There's nothing about the word coder that implies that it's an unpaid hobby. Nor that it's someone who works alone.
A better term to match that definition would be "lone unpaid coder".
I do agree with your main point James that if you're the kind of coder who works alone, then one of the most beneficial things you can do for your work and your career is to get more experience collaborating with others.
The reason I did choose "Coder" (if anyone is curious 😋) is that I find the term "Coder" does have the stereotype of a socially awkward nerd sitting in his mom's basement building role-playing games by himself.
And I just needed a really simple word to use 😂
I like your first comment too. This is a general framework that (by design) hasn't included things like freelancing, consulting, etc. and different fields like IOT, web, data analysts, etc.
My newsletter (where this article was adapted from) is starting to get into these differences though.
But I wanted this to start - like you said - by looking at it an easy way to get a top-level view/understanding.
Thanks for the comments!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great way to lay out the long-term strategy of a developer career. I'm a big believer in strategic thinking when it comes to career plans.
I want to respond with two points:
First, this is one possible career progression out of many. The starting point in any career plan is to ask yourself what your end goals are -- for example what's your dream job as a developer. Then make a progression plan (maybe like this one, or maybe different) towards that goal. In real life, careers have many more twists and turns, and much more ambiguity in terms of stages and titles.
Second, the article's definition of "coder" is entirely abritrary and I think it's inaccurate.
A better definition of a coder is: "someone who writes code." That's it. It could be an amateur or it could be a pro. There's nothing about the word coder that implies that it's an unpaid hobby. Nor that it's someone who works alone.
A better term to match that definition would be "lone unpaid coder".
I do agree with your main point James that if you're the kind of coder who works alone, then one of the most beneficial things you can do for your work and your career is to get more experience collaborating with others.
I agree 💯.
The reason I did choose "Coder" (if anyone is curious 😋) is that I find the term "Coder" does have the stereotype of a socially awkward nerd sitting in his mom's basement building role-playing games by himself.
And I just needed a really simple word to use 😂
I like your first comment too. This is a general framework that (by design) hasn't included things like freelancing, consulting, etc. and different fields like IOT, web, data analysts, etc.
My newsletter (where this article was adapted from) is starting to get into these differences though.
But I wanted this to start - like you said - by looking at it an easy way to get a top-level view/understanding.
Thanks for the comments!