Episode notes
Accountability is one of the most important concepts in your career—and one of the most frequently weaponized. In this episode, I unpack why so many of us have a visceral reaction to the word, and offer a pragmatic, functional definition that reframes accountability as something a good engineer actually invites. Drawing a parallel to software bug reports and root-cause analysis, I explain how healthy accountability creates clarity of expectation rather than surprise punishment.
Developer Tea
by Jonathan Cutrell · English · Tech & Science
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…
More from Developer Tea
-
E1311 · 21 Sep 2026 · 13 min
Fundamentals Will Help You Survive the Constant Acceleration of Software Engineering
Fundamentals get talked about constantly, but rarely defined. In this episode I dig into what a fundamental actually is — the building blocks, heuristics, and core characteristics that don't change — and why they matter more than ever in a profession where abstraction moves faster than almost anywhere else. If you feel like you can't keep up with every new framework, model, or tool release, the answer isn't to read faster. It's to step up a level.
-
E1310 · 5 Sep 2026 · 16 min
You Don't Learn Helplessness - You Learn Control
A 1967 study gave us the concept of learned helplessness — but the same researchers later reversed it. Passivity is our default state; control is what we learn. In this episode, I unpack what that neuroscience means for how you face hard things in your career, and why the action you take doesn't have to match the size of your problem.
-
E1308 · 21 Aug 2026 · 15 min
Why Reducing Complexity Is A Sign of Seniority
As you grow as an engineer, something counterintuitive happens: the systems you build get simpler, not more complex. In this episode, I explore why senior engineers tend to collapse abstractions, accept certain risks, and reduce the surface area they're responsible for — and what drives that shift underneath the surface. Understanding the reasons behind the trend is what lets you get there on purpose instead of waiting a decade to arrive there accidentally.
-
E1306 · 22 Jul 2026 · 19 min
Using Substition to Make Decisions Simpler
The skills you've built for reading people, reviewing code, and making calls under uncertainty all rely on the same brain shortcut: substituting an easier question for a hard one. In this episode, Jonathan explores how to take that automatic mental trick and use it on purpose — shrinking weighty, paralysis-inducing decisions down to the small, low-stakes actions they're actually made of.
-
E1305 · 10 Jul 2026 · 25 min
Your Single Most Important Tool for Managing the Uneven Downsides of Risk
The skills you build and the tools you master matter, but they aren't your most important asset when things go wrong — and something eventually will. In this episode, I work through why our careers and lives are governed more by avoiding catastrophic downside than by chasing upside, and why the single best tool for surviving a bad event isn't testing, insurance, or money — it's genuine trust with the people around you.
-
E1304 · 24 Jun 2026 · 19 min
Why Can't You Go Faster With AI? Focus on the Friction to Find Out
The skills you spent years building are getting cheaper to replicate—but that's not where the friction lives. In this throwback episode, I unpack why agentic coding hasn't made your team faster, and why the answer is the oldest model in the book: the theory of constraints. If you're a manager or a senior engineer being asked "why can't this go faster," this one's for you.
-
E1313 · 30 Sep 2026 · 17 min
How History Can Inform a Dynamic Understanding of Technological Revolutions Mirroring this Moment In Software Engineering
You're tired of hearing that you need to pick up AI, so today I'm not going to add to that pile. Instead, we'll look back at two moments in history that look a lot like this one: the arrival of Fortran in the 1950s, and the spread of autopilot in commercial aviation. Both show how new abstractions change the shape of our work without being purely good or purely bad.
-
E1303 · 18 Jun 2026 · 31 min
Software Engineering Principles That Still Hold Up in an Agentic World - Old Lessons Made New
The skills problem isn't going anywhere — it's just wearing new clothes. In this episode, I unpack how the lessons we learned decades ago (limiting work in progress, the theory of constraints, test-driven development) are coming roaring back as the fundamentals that will carry you through the agentic shift. The bottleneck has moved, and knowing where it went changes how you should work.
-
E1302 · 10 Jun 2026 · 28 min
Principles Oriented Thinking as a Durable Skill in an AI First World
The skills that survive every industry shakeup aren't the ones you can Google — they're softer, harder to name, and far more durable. In this episode, Jonathan explores principle-oriented thinking: the practice of stripping away the labels we attach to tools, roles, and even ourselves to see what something actually does at its core. It's the difference between handing your coding off to an agent and rethinking your entire workflow around what these new materials are truly capable of.
-
E1301 · 3 Jun 2026 · 28 min
What the Science Actually Says About Effective Feedback
Feedback is one of the hardest skills in any career, and most of us have only experienced a handful of moments where it actually drove positive change. In this episode, Jonathan explores how to give and receive feedback that leads to real growth — starting with setting your ego aside, getting clear on your goal, and using behavior-based models like SBI and Netflix's Four A's. It's a durable skill that turns a contentious, dreaded conversation into a genuine pathway to career development.
