Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
as i wrote in the end of my post.. i have to repeat those things to myself often, because I must say I still have some doubts. and no week passes without me thinking... maybe it would be better if I just code. that is what i do best.
but then I also see the impact I have as a technical lead, sometime is a question I make during a meeting, sometimes is just giving an hint on some technical issue, and I realize how much time and effort I spared to my team with that.
Yeah. I perfectly know those leads that are far away from the trenches, had many in my career and I definetely don't want to become one of them. Will try my best, and if doesn't work, I can always be back to coding. ( on the other hand, tech leads and engineering managers are needed, so why not trying to be one that is really useful, not only to the company but also to the team members? )
This is a great response.
Just because many have failed at the role doesn't mean we have to keep failing. It just means we need to grow from their mistakes.
I've been working 7 years as a software engineer, and I've been programming for 15 years now. I've seen outdated washed out leaders that just fill their spot and warm their chairs, and I've been honored with bright committed involved tech leads that have inspired and pushed me above and beyond.
I can only aspire to be a fraction as good as they are, and I'll be happy with my role.
They weren't the best at the minutia of day to day coding examples, but the moral in their decision making was impeccable, their ethics were remarkable, and they are to this day at the top of their game in knowledge of design patterns and best practices. All of this is framework agnostic and goes beyond coding. And that is what to me makes a great tech leader awesome.
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.
thanks for your comments.
as i wrote in the end of my post.. i have to repeat those things to myself often, because I must say I still have some doubts. and no week passes without me thinking... maybe it would be better if I just code. that is what i do best.
but then I also see the impact I have as a technical lead, sometime is a question I make during a meeting, sometimes is just giving an hint on some technical issue, and I realize how much time and effort I spared to my team with that.
Yeah. I perfectly know those leads that are far away from the trenches, had many in my career and I definetely don't want to become one of them. Will try my best, and if doesn't work, I can always be back to coding. ( on the other hand, tech leads and engineering managers are needed, so why not trying to be one that is really useful, not only to the company but also to the team members? )
This is a great response.
Just because many have failed at the role doesn't mean we have to keep failing. It just means we need to grow from their mistakes.
I've been working 7 years as a software engineer, and I've been programming for 15 years now. I've seen outdated washed out leaders that just fill their spot and warm their chairs, and I've been honored with bright committed involved tech leads that have inspired and pushed me above and beyond.
I can only aspire to be a fraction as good as they are, and I'll be happy with my role.
They weren't the best at the minutia of day to day coding examples, but the moral in their decision making was impeccable, their ethics were remarkable, and they are to this day at the top of their game in knowledge of design patterns and best practices. All of this is framework agnostic and goes beyond coding. And that is what to me makes a great tech leader awesome.