This is a widespread syndrome. It's not only in our industry of course but has real consequences in terms of leadership.

Interesting parable, it's indeed a good way to illustrate different leadership styles. Being more strategic is clearly what one should try to do.

A good way to frame the possible models for your organization regarding remote work. The GitLab Handbook stays a very good resource regarding remote work, they really thought about it and documented their findings.

A good reminder that long hours are not a sign of success with your project... on the contrary.

There's often confusion as to where the management responsibilities are in agile teams. This little rambling does a good job pointing it out and giving an idea of how management happens inside and around teams.

Indeed, it's not just about hiring people it's also about having a safe culture in the workplace.

Interesting idea. Didn't make one but maybe I should sit and take some time to do that.

It's indeed not only about skills but also about roles... and the natural tendencies to cover them.

This is still a good framework to think about what motivate developers in a team. Not everyone is the same.

An oldie but still a good one. Yes, the people matter but even good people won't strive in a badly designed system.

Indeed, it's hard. You need to put in the work but it's hard to predict where the real value will come from.

Interesting findings about procrastination. Some effects were expected, others less so. The actions to avoid it in teams should be well known now.

Interesting comparison of different definitions for software complexity (which is an ambiguous term to say the least). It leads to nice consequences when team dynamics are considered.

Juggling different roles isn't easy. It's indeed even harder when friendships are involved. Know which hat you're wearing at all times.

This kind of articles are always a bit caricatural. Still there is some good advice in there. Keep an eye open for the harmful behaviors.

Mistakes happen, but shrugging them off with blaming people or pushing them to be more careful is counter-productive. Instead, you want to find the organizational issues which made them possible in the first place.

If you expected another outcome on the average developer job from the LLM craze... you likely didn't pay attention enough.

You've see a co-worker doing this, right? They're unlikely to be spies, but still they're inadvertently using sabotage tactics.

I prefer aiming for egoless positions in teams... But if it doesn't work, I guess this little trick can help turn someone around.

Rituals are definitely important... if you understand why you're going though them. If you just "go through the moves" they're failing.