How to deal with a junior techlead?

Summary

In this video, Frederick addresses the challenges of dealing with junior developers who overstep their roles, acting as tech leads and product owners while micromanaging seniors. He emphasizes the importance of engagement and collaboration, pointing out that junior developers often take on these roles when seniors fail to contribute. Frederick suggests that seniors should actively participate in discussions to prevent juniors from filling the gap. When tensions arise, he recommends escalating the issue diplomatically to maintain a respectful and productive team environment, avoiding power struggles and fostering mutual respect.

Takeaways

• 😀 Junior developers may sometimes take on roles like tech lead or product owner, especially if senior developers are not engaging with them effectively.
• 😀 In the software development world, it's often not about who has the best solution, but who can make the best case for their approach.
• 😀 If a junior developer is acting as a micromanaging figure, it could indicate that the senior developer is not putting forward their own ideas or engaging in the process.
• 😀 It's important for senior developers to actively collaborate and engage with junior developers to create a balanced working environment.
• 😀 Juniors typically want collaboration and respect, and will be more likely to settle down if they feel heard and respected by seniors.
• 😀 Endless discussions and debates from any developer (not just juniors) can be frustrating, but they should be resolved by focusing on value creation and moving the project forward.
• 😀 In an expert democracy, decisions are made based on who can argue their approach best, so senior developers should aim to communicate effectively and avoid unnecessary debates.
• 😀 If a junior developer is persistently micromanaging, the senior developer should engage them diplomatically and bring others (e.g., product managers or stakeholders) into the conversation for resolution.
• 😀 Sometimes, using external input (like asking a manager for advice) can help break a deadlock and push forward the decision-making process.
• 😀 If a junior developer is consistently disruptive despite senior engagement, it may be time to involve a third party to help resolve the issue and avoid frustration among the team.

Q & A

What is the main issue the speaker addresses in the video?

The main issue is about a junior software developer who acts like a tech lead or product owner and micromanages senior developers, leading to frustration in the team.

Why does the speaker suggest the junior developer's behavior occurs?

The speaker suggests that the junior's behavior happens because the senior developers are not engaging enough with the junior, which leaves space for the junior to take on more responsibilities.

What does the speaker mean by 'expert democracy' in the context of software development?

In software development, 'expert democracy' refers to a decision-making process where the person who can make the best case for their approach typically gets their way, regardless of seniority.

How can senior developers avoid a junior taking on too much responsibility?

Senior developers should engage actively with juniors, share their ideas, and collaborate, which prevents the junior from filling the space left open by a lack of senior engagement.

What approach does the speaker recommend when a junior developer is micromanaging?

The speaker recommends engaging with the junior by expressing your own thoughts and opinions, and then escalating the issue by involving a manager or team to mediate and offer guidance.

What does the speaker mean by saying, 'it's like a parent who doesn’t care about their kid'?

The speaker uses this analogy to explain that if a senior developer does not engage with a junior, they are essentially allowing the junior to take on responsibilities and behave in ways that could have been prevented with proper interaction.

How does the speaker suggest resolving conflicts between a senior and a junior developer?

The speaker suggests that both the senior and the junior developer should discuss their perspectives, and if they can't agree, they should involve a third party (such as a manager or stakeholder) to help make a final decision.

What happens if the senior developer doesn't engage with the junior?

If the senior developer doesn't engage, the junior may continue to take on leadership roles and micromanage, which could eventually lead to frustration and poor team dynamics.

How does the speaker view the behavior of juniors who constantly voice opinions?

The speaker believes that juniors who constantly voice opinions are often eager to collaborate and are looking for engagement. The issue arises when the senior developer does not engage with them effectively.

What is the ultimate goal when dealing with a junior acting like a tech lead?

The ultimate goal is to maintain a good relationship with the junior, ensure they feel heard and respected, while also setting boundaries and making collaborative decisions to foster a healthy team dynamic.