Not a huge fan of the writing style and the pokemon metaphor. That said, seeing your growth as an engineer based on circles is spot on.

Interesting ideas about leadership lacking in impact. Indeed it should be seen as a communal function, it's not about individuals leading each in their own directions. Think about it in a systemic way.

Good points, this is indeed often where we are struggling when we move to a leadership role. This changes the nature of the work at least in part and we need to adjust to it.

I'm not sure the incentives are right... it's better to clean up as you go. Still some places would benefit from such an event from time to time and even if you clean up as you go missed opportunities happen.

Funny experiment at drawing parallels between engineering leadership and how you should behave when hiking in nature. This works surprisingly well.

Interesting tips and actions to help frame the conversation. The goal is to get the team better self-organized and directed.

This is indeed the best approach I've seen for brainstorming. It gives a chance to everyone to bring something forward, even the introverts.

A bit too archetypal for my taste but there's some truth to it. If you lean towards "explorer" (I think I do), it's hard to be also a leader. Now you could be aware of your flaws and put tools in place to compensate for them when you need lead.

This is an impressive piece about decision making and leadership. I love the approach: seeking to get the decision out of the person instead of deciding for them.

Interesting list. Definitely good things to try to learn there.

Interesting approach to get a better understanding and awareness of your surroundings as a tech lead or lead dev.

Nice (even though a bit long) explanation of the skills needed for a senior software engineers. Definitely a bunch of good advises in there.

Interesting framework for sustaining a strategic train of thoughts for the long term. This can't be a fix thing, it needs to live and breather which this approach seems to foster.

OK, unexpected introduction, still the advices are sound: teach, delegate, handle the hard cases.

Like it or not but the "manager" label indeed changes interpersonal dynamics.

I think this is a very good summary of what being in the position of a tech lead entails. I especially like the bottom line of this article: it's a constant balancing act between your heart or your mind.

Most of the points pushed forward in this article are things I've been trying to achieve for a long time. It also summarizes fairly well most of the topics I go through with tech leads or people growing in the position for coaching situations.

Very good piece, I agree with all the advices in there. That being said, it's often difficult to apply. This is because it requires quite a lot of self-awareness from teams and not everyone is willing to work on themselves to realize their weaknesses in the first place.

Also I'd stress one point which I don't find pushed enough in that article. Very often you want persons who might not make your team stronger now but will over time. This even works better in my experience. Hiring is a bit like gardening in a way: it's also about keeping in mind how the people joining the team will bloom in that particular context and how it'll improve the landscape.