Hacker News Reader

I agree with OP that writing a task in a non-core language is concerning, and also agree with you that there might be more going on.

I've worked with both types of team leads -- those that are there because they are technically proficient, as well as those that are good at handling the politics so the team doesn't and relies upon Sr. engineers to guide the project technically.

It's completely situational as to what is appropriate. Are you a 6+ person team in a large org (or in a small dysfunctional org)? Then you want some one who can handle the politics. Are you a 4 person team that owns your company's entire tech stack? Then you want someone who is really technically proficient.

Since OP mentioned the manager of this person, I suspect it's a larger org where politics is king, otherwise they would report to a VP or higher directly.

> Bringing people together, keeping the motivation of the team going, solving conflicts as soon as they happen. Also communicating with management (maybe you haven't realized that you are free to focus on the tech side because someone else is absorbing the drama?)

This is probably their strongest suit.

> Sometimes people are in a position for a reason. The ironic thing that could happen to you would be that someday you get that job and suddenly realize that it requires a completely different set of skills.

lol, indeed

> Sometimes people are in a position for a reason.

I agree with most of what you said, but sometimes people are in a position for the wrong reason. For example, they may have just been an old friend of the person who hired them.