You make a really good point. I only kinda disagree with the last part :
But can I really do all of this as a developer?
I'd argue that if you do all of this you're essentially doing the job of a tech lead, and either you won't have time to do your job as a developer, or you'll be working twice as many hours (making you only a 5x dev on a per hour basis 🤣).
Still I'll try to apply your advice, it's really tempting to just try and do the work yourself because you know you can, even though in the long run it's less effective than helping the team.
I didn't mean that you have to contribute to all of the areas I mentioned. Rather that it should be possible to contribute to any of them, even without an official title.
Also, you shouldn't try to do it completely on your own. If you have a reasonable manager, they should understand the benefits of your contribution to the team, and support you in your efforts - and understand that these efforts take time. Syncing with your manager will also help you contribute where it really counts instead of guessing on your own.
But you're also right that it is, to some degree, doing a job of a tech lead (or a principal developer, or an architect, or an engineering manager - depending on which area you'll choose to contribute to). But this is the reality of how you advance your career. To become a tech lead, you need to do some of the tech lead's work first, both to learn how to do it and to prove to your company that you can do it.
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.
You make a really good point. I only kinda disagree with the last part :
I'd argue that if you do all of this you're essentially doing the job of a tech lead, and either you won't have time to do your job as a developer, or you'll be working twice as many hours (making you only a 5x dev on a per hour basis 🤣).
Still I'll try to apply your advice, it's really tempting to just try and do the work yourself because you know you can, even though in the long run it's less effective than helping the team.
I didn't mean that you have to contribute to all of the areas I mentioned. Rather that it should be possible to contribute to any of them, even without an official title.
Also, you shouldn't try to do it completely on your own. If you have a reasonable manager, they should understand the benefits of your contribution to the team, and support you in your efforts - and understand that these efforts take time. Syncing with your manager will also help you contribute where it really counts instead of guessing on your own.
But you're also right that it is, to some degree, doing a job of a tech lead (or a principal developer, or an architect, or an engineering manager - depending on which area you'll choose to contribute to). But this is the reality of how you advance your career. To become a tech lead, you need to do some of the tech lead's work first, both to learn how to do it and to prove to your company that you can do it.