Re:Ask HN: What can set one up for success in a Tech lead role
by muzani on Sunday July 22, 2018 @12:00PM
(#17587344)
There seems to be a few descriptions of tech lead:
A. An engineer guiding the team, similar to a sports captain or a military team lead.
B. An engineering manager expected to write code during slow hours.
C. A superstar expected to give input in meetings and handle some of the project management and task distribution.
A is acceptable. B and C are not. I'd say the first thing you do is check whether it's B or C and turn down the role if it is, or convince them to use A.
Engineering often involves two types of work - managing and making. Managing means you need to always be available, sometimes all waking hours. Making means you are in a state of deep work, blocking off all distractions. These two do not go well together. If you take both jobs, you will do a terrible job at both, because they conflict with one another.
If I could hire one programmer, the first would be a full time programmer. If I could get two programmers, the second would be a full time manager, handling things from bug reports, clients, customer modeling, fundraising, technical meetings, project estimates, cutting down features, business logic, architecture, database design, and so on.
If you want to do type A, nearly everything should be under the role of a separate manager - documentation, SDK usage, architecture, designs. A tech lead is simply responsible to keep the manager up to date, and maybe handle things like deciding on arguments between someone and the manager.
A. An engineer guiding the team, similar to a sports captain or a military team lead.
B. An engineering manager expected to write code during slow hours.
C. A superstar expected to give input in meetings and handle some of the project management and task distribution.
A is acceptable. B and C are not. I'd say the first thing you do is check whether it's B or C and turn down the role if it is, or convince them to use A.
Engineering often involves two types of work - managing and making. Managing means you need to always be available, sometimes all waking hours. Making means you are in a state of deep work, blocking off all distractions. These two do not go well together. If you take both jobs, you will do a terrible job at both, because they conflict with one another.
If I could hire one programmer, the first would be a full time programmer. If I could get two programmers, the second would be a full time manager, handling things from bug reports, clients, customer modeling, fundraising, technical meetings, project estimates, cutting down features, business logic, architecture, database design, and so on.
If you want to do type A, nearly everything should be under the role of a separate manager - documentation, SDK usage, architecture, designs. A tech lead is simply responsible to keep the manager up to date, and maybe handle things like deciding on arguments between someone and the manager.