Interesting move on the Scrum definitions to move from roles to accountabilities. The article does a good job explaining it but then falls back into talking about roles somehow. Regarding the tech leads indeed they can work in Scrum teams. Scrum don't talk about them simply because Scrum don't talk about technical skills.

Nice musing about leadership in a technical context. It's indeed not completely about having all the answers, it's about facilitating the conversations and framing them properly.

Not fond of the metaphor used here which leads to quite some noise. Still, this article contains interesting ideas to try to push R&D initiatives forward. Definitely needed to improve any kind of organisation.

Nice post, and indeed it's not about Python if you read until the end. It shows that it's important to be able to make informed choices and not just pick your tech stack based on knee-jerk reactions.

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

This is indeed an interesting scale to keep in mind. Teams shouldn't get too big, or too small.

If regularly see people propelled tech leads without really knowing what it means. This short post is a good summary of the skills one needs to build to fit the role.

Interesting little taxonomy of staff engineer roles. This can help to know from where you're talking in your organization.

This article is spot on in my opinion. This resonates so much with my own experience and ethos... I guess I could have written that if my prose was any good.

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.