When should a manager step in?

When should a manager step in?
7 minutes by Charles-Axel Dein

Good managers balance stepping in with giving their team room to make mistakes and grow. According to Charles, decisions worth intervening on are those that could cause serious, hard to reverse damage, while style differences and minor disagreements are best left to the team. He adds that the right level of involvement also depends on how experienced someone is with a specific task. When stepping in, a good manager explains their reasoning and leaves the person still feeling ownership of their work.

Still writing tests manually? Meticulous AI is here
sponsored by Meticulous

Most teams are forced to make the tradeoff between better coverage and more maintenance effort. But top engineering teams like Notion, Dropbox, Wealthsimple and LaunchDarkly have discovered a new testing paradigm. Built by ex-Palantir engineers, Meticulous creates and maintains E2E UI tests that covers every edge case of your web app - without any developer effort, making it the only tool to improve both product quality and dev velocity.

How to handle overly confident and combative colleagues
4 minutes by Yue Zhao

Working with a combative colleague is draining, but Yue says two simple approaches can help. First, sidestep conflict by building on their ideas rather than challenging them, which lowers their guard and gets your voice heard. Second, use soft, belief-based language instead of data arguments to reframe their views as opinions, not facts, opening space for your ideas. Yue suggests to practice both approaches regularly so they feel natural when you need them.

Staff engineers need to get hands-on again
6 minutes by Paula Muldoon

AI tools are making experienced engineers far more productive, which changes what a staff engineer should focus on. Paula points out that features that once took a week now take a day, so staying hands-on is essential to make good technical decisions. Customer impact should replace org impact as the key measure of success. Paula's advice is to get back to building, learn from junior engineers who are ahead on these tools, and let results speak for themselves.

Architecture is not a blueprint but a set of decisions
12 minutes by Scott Millett

Good architecture is not a master plan but a small set of shared decisions that keep independent teams moving in the same direction. Like a shipping container standardizing global trade handoffs, architectural constraints let everything else evolve without breaking apart. These decisions are always trade-offs, and they shape teams as much as systems, since organizational structure and system structure mirror each other. The goal is influence, not control.

My heuristics are wrong. What now?
4 minutes by Marc Brooker

Experienced tech leaders risk giving outdated advice as AI tools rapidly change what's easy, hard, or even possible in software. He points out that old rules about system design, code quality, and API boundaries may no longer apply but the solution is simple: get hands-on again. He suggests to build real things, run experiments, and actively update your instincts to stay genuinely useful to your team.

And the most popular article from the last issue was:

• Interviewing tactics for a post-LLM world