It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.
Episode 343: Tech lead/manager and discouraging seniors
In this episode, Dave and Jamison answer these questions:
-
A listener named Mike asks,
I’ve been offered an Engineering Management position at a company I previously worked for. The team is very small and composed of juniors and mid-level developers. The role is also completely new and because of the size and experience of the team there is some expectation that the manager will also have a fair amount of involvement in PR reviews and likely also writing some code. Is this common? Do you feel like a manager can also be a team lead from a technical perspective on a day to day basis? What should I be thinking about when considering this role?
-
How do I keep up juniors’ morale regardless of bad code/ideas? I work in a team of 4-5 developers. We have one junior, one mid (me), one senior and our team lead. I think we mostly work well. However, sometimes the senior and team lead sort of talk down at the junior. For example, in a meeting talking about how to solve a problem the junior will propose an idea, but the senior and/or both team lead would respond by saying that no its not a good idea which is fine. However the tone of the voice often hints ‘oh you should know this it’s obvious you jamoke’.
The junior has started to stay quiet and has told me he doesn’t feel comfortable asking the seniors for help. I’ve interjected in meetings to say I understand why the junior might have this idea but I don’t think it’s the best solution. What should I do? Should I talk to the senior/team lead? Do I just let it play out?