Clearer thinking for working software teams.
Developer Tea treats software work as a series of thinking problems, not just technical tasks. Short episodes reason through team rituals, AI-driven change, career growth, tradeoffs, risk, and the habits that make senior engineers more useful.
PRESS PLAY
Developer Tea is a compact, reflective show for software professionals who want better judgment around their work. Its episodes tend to start with a practical tension. AI is changing the job quickly. Team process can feel restrictive. Careers can drift while people wait for approval, feedback, or the next clear opportunity. From those starting points, the show slows the problem down and asks what must be true for better outcomes to happen. Recent episodes return often to the responsibilities of seniority. Senior engineers are not only people who know more syntax or make faster choices. They are people who can hold multiple tradeoffs in mind, explain the cost of a decision, and look for a third option when two goals seem opposed. The show also treats management and team habits as design problems. Ceremonies, prioritized backlogs, demos, and performance conversations are framed as tools for creating order, feedback, and shared expectations. That gives the show a useful middle ground between career advice and organizational thinking. It talks about resumes, but as a proxy for measurable impact and self-directed career ownership. It talks about tooling, but as part of shaping an environment where repeated work has less friction. It talks about risk, but with attention to backup plans, human error, and the asymmetry between incremental wins and catastrophic losses. It talks about large fuzzy problems, such as tech debt or performance management, without pretending they can be solved once. The pace is calm and deliberate. The argument usually matters more than the anecdote. Listeners get concepts they can test immediately against their own code reviews, planning meetings, interviews, backlogs, and team rituals. Developer Tea is best when it names a pattern that busy engineers already recognize but have not had time to define. Its value is not hype or hot takes. Its value is disciplined clarity for people building software inside changing systems.
Made for: Developer Tea is for software engineers, senior engineers, engineering managers, and engineering leaders who want practical language for better decisions. It especially suits people navigating AI change, career growth, team process, and ambiguous organizational problems.
What sets it apart: The show stands out by turning abstract workplace ideas into concrete engineering examples without becoming either a management seminar or a tools roundup. Its short format makes room for careful reasoning, tradeoff analysis, and grounded career advice.
Developer Tea exists to help driven developers connect to their ultimate purpose and excel at their work so that they can positively impact the people they influence. With over 17 million downloads to date, Developer Tea is a short podcast hosted by Jonathan Cutrell, engineering leader with over 15 years of industry experience. We hope you'll take the topics from this podcast and continue the conversation, either online or in person with your peers. Email: [email protected]
Based on 4 episodes we listened to · September 2026
Developer Tea makes engineering leadership more legible by tracing team problems back to cognitive demands, incentives, and the routines that shape daily work.
Developer Tea turns engineering management into a series of compact reasoning exercises. Jonathan Cottrell takes one workplace idea at a time, then tests it against recognizable situations involving code review, prioritization, team meetings, and changing expectations around…
A code review request goes unanswered; Jonathan Cottrell asks what would make you answer next time.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A clear case for keeping team rituals and regularity intact as change speeds up.
The episode treats AI change as the backdrop, but it keeps circling back to a more ordinary problem: how a senior engineering leader prevents a team from drifting into disorder. Its argument is plain enough.
A calm reset that treats the tool set as part of the work environment.
Developer Tea takes a familiar engineering annoyance and turns it into a wider point: the friction in repeated work says as much about the tool set as the work itself.
A clear case for treating heuristics as tools, not truth.
It treats a familiar engineering trap seriously: the idea that sharper thinking alone can carry a career. The point is more measured than that. Clear judgment, better decisions, and steadier planning can improve results, but they do not explain success on their own.
A clear look at forcing functions and the behavior they quietly shape.
Developer Tea treats forcing functions less like a management buzzword and more like a way to notice what happens after the first decision. The examples move from code coverage targets to prioritized backlogs to all-hands and demo settings, and each one asks the same practical…
Behavior change starts with the trigger, the incentive, and whether action is actually possible.
This piece treats behavior change like a practical systems problem, not a lecture about rules or willpower. It works best when it shifts attention to the trigger, the incentive, and whether someone can actually act on the request.
A practical look at load, boredom, and work fit.
Developer Tea treats cognitive load as a useful way to read work, not as a buzzword. It connects the idea to how a day is planned, how a sprint is shaped, what gets handed off, and how much focus a person can reasonably give in the moment.
Long-form interviews on AI coding agents, infrastructure, and security, plus a recurring SED News roundup.
Founders and engineers on AI coding agents like Claude Code, and supply chain security.
Stack Overflow's Ryan Donovan interviews founders and engineers on AI agents, protocols, and dev tools.
Michael Kennedy interviews Python maintainers on packaging, security, web tools, and AI.
Michael Kennedy and Brian Okken run down the week's Python tooling, typing, and packaging news.
Matt Stratton interviews DevOps practitioners on security, platform engineering, and trusting AI-written code.
This episode explores how systems, whether intentionally or accidentally designed, shape outcomes for developers seeking clarity and purpose in their careers.
This episode discusses how building vocabulary—both literal and metaphorical—is a fundamental skill for career resilience, especially for developers and engineers navigating transitions and disruptions like AI.
This episode explores a meta-habit used by high-performing managers and engineers to unlock career growth and prevent burnout by optimizing energy expenditure.
This episode announces a new series called the Career Growth Accelerator Series, designed to help engineering professionals overcome career roadblocks and advance into leadership roles through practical exercises and guidance.
This episode explores how AI is fundamentally transforming software engineering by reducing the amount of code engineers write and shifting their role toward managing agentic workflows.
This episode introduces a basic thinking tool or model to help prioritize and understand the importance of items in a backlog, such as bugs or tasks, without offering a magic bullet solution.
This episode introduces the sports concept of forced and unforced errors as a mental model for developers to improve career decision-making and performance.
This episode explores the psychological concept of locus of control and how understanding internal versus external perspectives can help engineers take charge of their career outcomes.
This episode explores how AI is fundamentally changing the software industry from a business perspective and what it means for software engineers' careers, roles, and teams.
This episode addresses the misconception that becoming a senior engineer requires leading projects, emphasizing instead the importance of demonstrating ownership in one's work.
This episode explores how software engineers can navigate AI-driven job market changes by developing mental models for career advancement without compromising their values.
This episode explores burnout as a workplace syndrome defined by the ICD-11, focusing on how developers and managers can address it beyond just reducing hours.
This episode explores why maintenance tasks are often neglected through psychological concepts like the marshmallow test and hyperbolic discounting, explaining how people prioritize immediate rewards over future benefits.
This episode discusses how decision-making is becoming a core skill for software engineers, focusing on advanced techniques and the impact of AI tools on collaborative processes.
This episode shares personal vulnerability about job loss due to AI outsourcing and offers career advice for knowledge workers facing industry changes.
This episode discusses how to de-risk your career by identifying personal vulnerabilities and factors that influence decision-making, with a focus on developers.
This episode explores the management principle 'what you measure gets managed,' discussing its implications for engineering teams and organizations through examples like time tracking and surveillance software.
This episode advises developers to focus on primary career improvement paths rather than getting distracted by minor optimizations and office politics.
This episode introduces the Career Growth Accelerator series, focusing on helping mid-to-senior level developers overcome career hurdles and transition into leadership roles.
This episode introduces the concept of logarithmic returns as a meta-model for understanding how certain operations or relationships improve over time with diminishing returns, drawing parallels to algorithmic complexity and mathematical graphing.
This episode explores how people use substitute questions as cognitive heuristics to simplify complex decisions, such as choosing restaurants based on reviews or career paths based on past enjoyment.
This episode explores how to prepare for uncertain future events by building resilience and adopting general preparedness principles rather than focusing only on specific predictable scenarios.
This episode features an interview with Bryan McCann, CTO of You.com, discussing how AI impacts engineering, art, and organizational structures.
This episode explores how deliberate practice, distinct from mere repetition, can elevate engineering leadership skills by providing clarity on its definition and practical application in a developer's career.
This episode provides tactical strategies for taking ownership of your time by reducing obligations and meetings to combat burnout and increase personal agency.
This episode explains how well-positioned goals can provide clarity, perspective, and purpose in career development, especially for developers without formal coaching.
This episode discusses Chesterton's Fence, a concept cautioning against hastily rewriting or discarding existing projects or processes without first understanding their original purpose.
This episode addresses the tension between pursuing higher pay and maintaining meaningful work in career development, prompted by a listener's question about balancing money, meaning, and skill transitions.
This episode explores the tension between iterative planning and target state planning in software development, examining how these approaches can coexist and complement each other.
This episode argues that striving for perfection is not only unnecessary but dangerous because it is fragile and can negatively impact careers and personal life.
The host celebrates the podcast's 11-year anniversary and expresses gratitude to listeners while introducing the theme of helping developers find purpose and clarity in their careers.
This episode explains the principle of establishing baselines to effectively detect and measure change in your career and life.
This episode introduces a nine-block mapping exercise to help developers assess their skills, potential, and energy investment for sustainable career growth and purpose.
This episode explores why developers should tackle difficult tasks they've been avoiding, examining the human tendency to seek shortcuts and the importance of embracing necessary challenges in work and life.
This episode explores the principle that your current systems—including organizational processes, policies, and cultural effects—are perfectly designed for your outcomes, emphasizing personal responsibility for career growth.
This episode discusses why high-performing employees might not receive promotions during performance review season and explores two main reasons for this disconnect.
This episode features an interview with Bryan McCann, CTO of You.com, discussing AI, engineering, art, and philosophical perspectives on technology.
A personal reflection on navigating a job resignation that coincided with company layoffs, exploring the complex emotions and strategic timing involved.
Jonathan shares his personal experiences with tools, observations, and thoughts in the tech industry to help developers gain perspective and reduce overwhelm.
The host discusses how intrinsic motivation from personal interest in coding as a hobby was more powerful than external rewards like pay, and explores this concept to help developers overcome career stagnation.
This episode guides developers through two fundamental thought experiments to connect values and priorities with productivity, helping them find clarity and purpose in their careers.
This episode introduces a high-leverage habit for professionals at all levels that requires no special skills but thoughtful communication to reduce risks and improve career success.
This episode explores how defining problems rather than following predetermined career paths can help developers overcome roadblocks and achieve meaningful career growth.
Developer Tea examines why software engineers and leaders should prioritize limiting severe downside over pursuing equally large gains.
Developer Tea host Jonathan Gautrel argues that agentic tooling revives older software-engineering lessons, especially limiting work in progress and protecting focus.
Developer Tea frames "principles-oriented thinking" as a durable skill for software engineers, using the Apollo 13 sock repair to show how stripping a label reveals what a thing can actually do.
Everything is moving.
Start with the friction.
Clear thinking can become a trap.
Jonathan Cutrell discusses resume-driven development, emphasizing that building a strong resume requires focusing on measurable impact and setting clear goals.
Jonathan Cutrell discusses how the ability to synthesize multiple optimization factors, such as performance and maintainability, distinguishes senior software engineers from juniors, offering practical advice for career growth and interview success.
This episode explores the importance of backup plans in a developer's career, using risk-reward curves to show how catastrophic failures can outweigh incremental successes.
Jonathan Cutrell explores the concepts of second and third-order consequences in software engineering management, showing how actions create ripple effects.
Jonathan Cutrell introduces the philosophical concept of hyperobjects—large, intractable problems like global warming—and applies it to engineering challenges such as tech debt and performance management.
Jonathan Cutrell explores a model for behavior change based on trigger, incentive, and ability, applying it to management and self-improvement in software engineering.
Jonathan Cutrell explores cognitive load theory and its practical implications for developers and managers.
This episode discusses how to reframe areas for growth identified in performance reviews with your manager, moving beyond viewing them as a simple to-do list for improvement.
This episode discusses how employees often assume their managers provide adequate feedback and offers a practical tool to proactively request forward-framed feedback to improve workplace performance.
Jonathan Cutrell introduces a new management tool for developers, a quadrant framework for thinking about product lifecycle governance.
An engineering manager shares tools and tactics for effective engineering management, relevant to both managers and individual contributors.
This episode explores how philosophical frameworks unconsciously influence decision-making in professional and personal contexts, focusing on predicting and shaping the future amid disagreements.
The host shares a personal story about his father's cardiac event to discuss preparing for unexpected events in life and work.
The episode discusses two common misconceptions about human behavior that developers should recognize to improve their work and career.
Jonathan Cutrell provides practical tools for engineering teams to become more action-oriented during planning phases.
This episode introduces a tool to pair with the five whys exercise, focusing on matching actions to intentions to help operationalize goals like New Year's resolutions.
The host challenges listeners to iterate on their New Year's resolutions, emphasizing that true change requires more than just a choice.
The host celebrates the 10-year anniversary of Developer Tea, reflecting on the show's journey and its focus on helping developers connect with their purpose.
The host discusses pitfalls in planning ill-defined work for engineering teams, urging developers to think like leaders when estimating costs.
This episode discusses traits that distinguish senior engineers from junior ones, focusing on a psychological factor that helps engineers gain influence.
The host discusses the value of experience in a developer's career and draws an analogy from the aviation industry.
This episode discusses self-coaching techniques for developers, emphasizing that internal coaching complements rather than replaces external feedback.
The host challenges the common advice to maximize performance reviews, suggesting that doing nothing might be a better career strategy.
This episode discusses practical tactics for engineering job searches, including how to use company values in interviews, featuring career coach Brian Pulliam.
This episode features an interview with career coach Brian Pulliam, who applies the scientific method to engineering job searches, offering practical tools and structured coaching sessions.
The host introduces a simple framework for managing complexity and prioritizing tasks in a developer's daily work.
This episode shares two counterintuitive tips for interview preparation that also apply to other one-on-one conversations.
The host introduces two often-confused concepts that apply to any cooperative group, aiming to provide clear definitions to help developers gain perspective.
The host introduces two basic principles that underlie all productivity and career advice for software engineers.
Jonathan Cutrell explains the concept of classes of service in Kanban and how cost of delay curves can help prioritize work.
The host explains the abstract goal of the show to help developers find purpose and clarity, using the show's own goal-setting as an example for listeners to apply to their own problems.
The host reflects on nine years of the podcast and introduces a topic about configuring your brain for change.
The episode explores what constitutes a bad plan in software development, emphasizing the importance of aligning intentions and goals.
This episode explores the Lollapalooza Effect in project planning, using positive and negative examples to illustrate how combined forces can derail or enhance planning processes.