Re:Lessons learned as a software developer turned project ma...
by altdataseller on Thursday May 26, 2022 @12:35PM
(#31520404)
Grass is always greener. If you’re a team lead, you’re constantly in meetings and never using your creativity skills. If you’re just a coder, you have no say in the architecture. Optimal situation is just be a 1-person lifestyle startup
[ Parent
| on HN ]
Re:Lessons learned as a software developer turned project ma...
by gwbas1c on Thursday May 26, 2022 @02:53PM
(#31522076)
When I was a team lead, I rarely was in meetings. About 60% of my time was coding, the rest was reviewing others' work, giving direct technical guidance to team members, and answering questions from upper management. Typically upper management communicated asynchronously and didn't pull me into meetings on a daily basis.
An organization that has a team lead constantly in meetings is horribly mismanaged; and is looking for a talking head to boost someones' ego.
Re:Lessons learned as a software developer turned project ma...
by mmargerum on Thursday May 26, 2022 @04:04PM
(#31522748)
You have to be in a very functional organization to enjoy life as a tech lead . Otherwise you just end up a manager who knows how to code.
Re:Lessons learned as a software developer turned project ma...
by t43562 on Thursday May 26, 2022 @12:39PM
(#31520464)
The team lead does have a little authority to go with the responsibility whereas the Senior Developer tends to be given things to be responsible for without any authority to do them. But I agree about endless meetings and very little joy of coding.