💯 I was there and had to do exactly this - learn on my own and set my own expectations with where I wanted to go in my career.
A good rule of thumb is to look up to people who have already achieved what you want (which shouldn't be simply the title of "senior developer").
Want to be a competent senior dev? Look in the broader community for people who are considered great seniors devs.
It's true, there are SO many developers who stay with the same company doing, mostly, the same stuff and are given new titles just because they've been there for X years.
there are SO many developers who stay with the same company doing, mostly, the same stuff and are given new titles just because they've been there for X years.
💯 I was there and had to do exactly this - learn on my own and set my own expectations with where I wanted to go in my career.
A good rule of thumb is to look up to people who have already achieved what you want (which shouldn't be simply the title of "senior developer").
Want to be a competent senior dev? Look in the broader community for people who are considered great seniors devs.
It's true, there are SO many developers who stay with the same company doing, mostly, the same stuff and are given new titles just because they've been there for X years.
Erik Dietrich (@daedtech ) has written about this phenomenon while identifying a career-path 'black hole' of the "expert beginner": daedtech.com/how-developers-stop-l...
Sweet - thanks for the link! I read this one in a galaxy long ago but will be re-reading. Erik's stuff is gold 👍
Thanks for the mention!