If you're an engineering leader right now, everything around you feels like it's changing at once — new tools, new processes, new expectations. It's tempting to accept chaos as the new normal, but in today's episode, I make the case that your job is to go on the offense and *create* order. Not by clinging to old processes, but by becoming the groundskeeper of your team's ceremonies — the regular, repeated actions that give your team a foundation to actually improve from.

• Humans Are the Limiting Factor (And That's Okay): Our fundamental cognitive capabilities haven't changed in tens of thousands of years. Progress is collective — better tools, better documentation, better knowledge systems — but individually, our brains work the same way they always have. Any process that involves humans has to account for this.
• Why Ceremony Matters More Than Ever: Whether you call them scrum ceremonies, team rituals, or just "the way we work," regular and repeated team actions aren't bureaucratic overhead. They're how humans learn, build comfort, and reduce cognitive load. Just like sitting in the same seat at your coffee shop or driving the same route to work, repeated patterns free up mental energy for the things that actually require your attention.
• Regularity of Action Over Specific Process: This isn't a prescription for scrum or kanban or any particular framework. The point is that your team has some determined, repeated way of doing things — whether that's a weekly planning session, a daily standup, or a trigger-based refinement process. The specific process matters less than the consistency.
• Ceremony Enables Experimentation: If you want to get better, you need to be able to change one variable at a time and measure the result. That's impossible when everything is changing at once. Holding your core processes steady gives you the controlled environment you need to actually learn what's working and what isn't.
• Spot the Anomalies: When you maintain regularity, deviations become visible. If productivity dips but your ceremonies stayed constant, you have a much better shot at diagnosing what actually changed. Without that baseline, every signal gets lost in the noise.
• Episode Homework: Sit down with your team this week and talk about what your ceremonies are. What do you want to hold constant? What do you want to be true on a regular basis? Name them, write them down, and commit to tending them — even as everything else shifts around you.

No matter what you're building, SerpApi is the web search API for your needs. If you're building an application that needs real-time search data—whether that's an AI agent, an SEO tool, or a price tracker—SerpApi handles it for you. ● Make an API call and get back clean JSON. ● They handle the proxies, CAPTCHAs, parsing, and all the scraping so you don't have to. ● They support dozens of search engines and platforms, and are trusted by companies like NVIDIA, Adobe, and Shopify. ● If you're building with AI, they even have an official MCP to make getting up and running a simple task. Get started with a free tier to build and test your application before you commit. Go to serpapi.com.

If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.

If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community today!

We are developing a brand new newsletter called The Tea Break! You can be the first in line to receive it by entering your email directly over at developertea.com.

Your tool set isn't just a collection of utilities — it's the environment you live in every day, and it's shaping you whether you realize it or not. In today's episode, I explore two principles that senior engineers consistently apply to their workflows, regardless of which specific tools they're using. As our industry goes through one of the most rapid periods of change in the last 20 years, the engineers who thrive won't be the ones chasing every new tool — they'll be the ones who obsess over reducing friction in the work they do most often.

• Honor the Grief: Many engineers are experiencing a real sense of loss as the deep cultural connections to languages, communities, and hand-written code begin to shift. Recognizing and processing that grief — rather than letting it turn into reflexive rejection of new tools — is essential to thinking clearly about what comes next.
• "We Shape Our Tools, Then Our Tools Shape Us": Your tools aren't neutral. A bad monitor height, a faulty keycap, or a clunky deployment process all shape you back — draining focus, breaking flow, and compounding over time. The most senior engineers treat this relationship as a first-class concern.
• Principle 1 — Tools Are Your Environment: There's a spectrum from "tool" to "environment," and most of what you work with sits somewhere in between. Your terminal, your desk, your claude.md file — all of these are environment. Sharpening your tools means shaping your environment, and shaping your environment is sharpening your tools.
• Friction Is the Lever: You don't need a dramatic overhaul to change your behavior. Tiny reductions in friction — a two-letter alias, a key binding to run tests, setting your shoes out the night before — have an outsized effect on how often you actually do the things you want to do. James Clear's Atomic Habits framework applies directly to engineering workflows.
• Principle 2 — First Order Thinking: Borrowed from Adam Savage's concept of "first order retrievability," the idea is simple: identify what you do most often and invest in making that better. Not faster, not just automated — better. If you do something a hundred times a day, even a small improvement compounds dramatically.
• Invest in the Fundamentals: Your standups, your one-on-ones, your specifications, your prompting skills — these are the repetitive, high-frequency activities where your biggest growth opportunities live. Stop assuming you've "arrived" on the basics just because nobody is giving you negative feedback.
• Episode Homework: Look around your workspace right now — physical and digital. Identify one thing you do repeatedly where friction is slowing you down or discouraging follow-through, and make one small change to reduce that friction today.

No matter what you're building, SerpApi is the web search API for your needs. If you're building an application that needs real-time search data—whether that's an AI agent, an SEO tool, or a price tracker—SerpApi handles it for you. ● Make an API call and get back clean JSON. ● They handle the proxies, CAPTCHAs, parsing, and all the scraping so you don't have to. ● They support dozens of search engines and platforms, and are trusted by companies like NVIDIA, Adobe, and Shopify. ● If you're building with AI, they even have an official MCP to make getting up and running a simple task. Get started with a free tier to build and test your application before you commit. Go to serpapi.com.

If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.

If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community today!

We are developing a brand new newsletter called The Tea Break! You can be the first in line to receive it by entering your email directly over at developertea.com.

If you're enjoying the show and want to support the content head over to iTunes and leave a review!

• When Good Thinking Becomes Overthinking: Discover why the pursuit of perfect analysis often undermines good decision-making. Loading every caveat, every exception, and every alternative into your working memory doesn't produce better outcomes — it produces paralysis.
• Heuristics as a Feature, Not a Bug: Your brain is an efficiency machine that creates shortcuts — cached concepts, stored routines, snap judgments. These heuristics are always incomplete, but they let you move through complex problems quickly. The opportunity is to deliberately choose which heuristics to exploit.
• "All Models Are Wrong, Some Models Are Useful": Useful illusions don't need to be perfectly true. They need to be true enough that acting on them produces better outcomes than endlessly debating their accuracy.
• Useful Illusion: Coding by Hand Is Going Away: Whether or not this is literally true in every case, the engineer who acts as if it is will invest in agentic workflows, LLMs, and new tooling — while the engineer who picks the argument apart risks being labeled a skeptic and falling behind.
• Useful Illusion: Hard Work Pays Off: You can poke holes in this all day — wrong direction, burnout, culture-dependent — but people who follow this heuristic tend to build reputations as reliable and capable. Few of us want to be known for the opposite.
• Useful Illusion: As Long As I'm Learning, I'm Growing: Learning becomes less directly correlated with career advancement over time, but continuing to act on this belief keeps you flexible, curious, and in a growth mindset.
• More Useful Illusions for Your List: Clean code is better. Always think about the user's experience. Go with the tool you know. Volume of delivered work correlates with career success — especially during performance review season.
• The Key Insight: You don't have to believe any of these things literally. You're exploiting your own heuristic system to drive efficient action and avoid wasting time on low-utility debates. The result is a more decisive, action-oriented version of yourself.

Your coding agents have access to your codebase, but access doesn't mean good context. Agents can't easily reason across MCPs without guidance — they don't know your architectural decisions, your team patterns, or what that acronym actually means. Unblocked is the context layer your agents are missing. It synthesizes your PRs, docs, Slack messages, and JIRA issues into organizational context so agents make better plans, write higher quality code, use fewer tokens, and require fewer correction loops. Get a free three-week trial at getunblocked.com.

If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.

If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community today!

We are developing a brand new newsletter called The Tea Break! You can be the first in line to receive it by entering your email directly over at developertea.com.