Stuck on a name? I built `/evolve` for pi.dev — genetic-programming-style brainstorming.
Seed it with anything:
• `/evolve project name for a tool that merges contacts`
• `/evolve book title in the vein of "Interviewing in the post-LLM world"`
• `/evolve talk title about observability burnout`
Pick the one you like → it mutates 5 more. Repeat until it clicks. ✓ Finalize drops it into your editor.
`pi install npm:pi-evolve`
Grab the latest update and let us know what you think!
No, there's no magic checklist for building a high-performing team (we wish!), but this chapter gives you the practical tools to get there: designing communication channels that actually work, building a shared knowledge base, and shaping processes that empower autonomy.
From tackling the hidden cost of private messages to designing team inboxes inspired by the actor model, Chapter 4 is packed with concrete, actionable advice.
📖 New chapter just dropped!
We've published Chapter 4 of Engineering Manager's Compass and it's now available on Leanpub!
Let's meet this June in Amsterdam at a special TechLead Conference Edition: AI in Orgs where I will be speaking about interviewing tactics for a post-LLM world
More information about the conference - https://techleadconf.com/ #TechLeadConf
Join us at the TechLead Conference and take your professional development to the next level! Gain valuable insights on navigating AI adoption in organizations and reducing system complexity. Network with like-minded professionals, learn from senior engineers and tech leads who will share practical insights from the trenches. Get mentored by experienced team leads and explore diversity and inclusion, talent management, and career growth. Enhance your leadership and teamwork skills and build valuable relationships in the tech industry. Register now!
The "Absence Test": How do you know when your team has autonomy?
🚨 The "Absence Test": How do you know when your team has autonomy? A couple of years ago, I had to take emergency leave for two weeks. My team was in the middle of a big project and I was worried about how things would go without me. To my surprise, most things went smoothly yet there were still a few hiccups that reminded me of wise advice I once received: "You know you're a good manager when you can go on vacation and your team doesn't even notice you're gone." 🔍 THE ABSENCE TEST The Absence Test is a thought experiment where you imagine completely stepping away from your team for an extended period. It's designed to reveal the gaps in your team's autonomy and help you build better processes. How to Apply It: 🏖️ Method 1: Take your regular holidays and, upon return, interview your team and stakeholders to identify which tasks were hampered during your absence. 👥 Method 2: Delegate your responsibilities to a PM counterpart or senior team member for a period. This also helps senior engineers grow by exposing them to management tasks. The key is resisting the urge to intervene when fires arise. That's where the real learning happens. 💡 WHAT YOU'LL DISCOVER After this exercise, you'll get a clear picture of what needs attention: ✅ The presence of the right processes: • Clear decision-making frameworks that don't require your input • Well-documented knowledge and procedures • Team rituals that function independently • Feedback loops and metrics that keep the team self-monitoring ❌ The absence of the wrong processes: • Bottlenecks that route through you • Hero culture and constant firefighting • Information hoarding • Unnecessary approval dependencies ⚠️ A WORD OF CAUTION This approach isn't about becoming lazy or disengaged. There's a balance to strike: • Avoid complacency: Don't let team efficiency become an excuse for reduced effort • Keep growing: Your reach might stay small if you optimize purely for team independence • Balance efficiency vs. career growth: You still need to grow your team, not just make it more efficient 🎯 THE BOTTOM LINE We should focus on building environments with the presence of the right processes and the absence of the wrong ones. The Absence Test reveals which is which. ━━━━━━━━━━━━━━━━━━━━━━ Have you ever tried stepping back to test your team's autonomy? What did you discover? I'm considering writing a more detailed guide on this topic and would love to hear your thoughts and experiences in the comments. #EngineeringManagement #Leadership #TeamAutonomy #Management #TechLeadership
Many tech companies strategically exaggerate their technologies, not just to impress investors or the public, but to mislead competitors and protect their edge. From Google’s PageRank spin and Apple’s secretive codenames to today’s AI hype, the pattern is clear: secrecy and marketing often blur the line between real breakthroughs and clever storytelling. The article reminds us to stay critical, question the hype, and remember that what’s claimed isn’t always what’s real.
https://blog.incrementalforgetting.tech/p/the-ai-lie?r=1tixy7
A practical guide to navigating compensation and promotion conversations at work. I break down key concepts. If you're looking to have more effective compensation conversations backed by data rather than emotion, you might find these strategies helpful.
Did you know that your organization's structure directly impacts the software you build? Conway's Law highlights the deep connection between team dynamics and system architecture. By aligning your teams with your desired technical outcomes, you can create a virtuous cycle of innovation and efficiency. Learn how to map, analyze, and optimize this relationship to drive positive change in both your organization and your technology.
https://blog.incrementalforgetting.tech/p/how-your-organization-shapes-your?r=1tixy7
