Life Tech Stack | Developer Productivity Beyond Work

What do you do when the project you prepared for is no longer the priority? In our first Honest Answers segment, Erika and Bethany respond to a listener's question about a last-minute change of plans. They discuss how communication can make a change feel less arbitrary, why context switching leaves unfinished work on your mind, and how stopping notes, handoff documentation, and an AI-assisted morning routine can help you pick work back up. They also cover keeping a record of contributions when projects don't ship, separating your identity from your assigned work, and the loss of autonomy that can come with a reorg. The conversation turns to disagree and commit, the psychological safety it requires, and recognizing when it may be time to find a different team or role. To close, they translate some familiar corporate memos into plain language.

What does Stack Overflow’s 2026 Developer Survey reveal about software engineering, career insights, and engineering culture? The Overcommitted hosts unpack the findings, discuss what they mean for developers, and share the trends they’re watching across the profession.

Roxy Rodriguez-Becker taught middle school math, moved into the school library after earning a master's in library and information science, and then taught herself to code while raising three kids. She is now a developer community manager at Torc and the host of the She Ships podcast. In this episode she walks through what that transition actually required: the four AM club, waking up to study until she rushed out the door to a five AM gym session, working through 100Devs, and treating the job search as a numbers game with fifty to sixty outreach messages a week. She is candid about the burnout that followed and what it took to come back from it.The conversation also digs into networking as a skill rather than a personality trait. Roxy describes going to her first conference and barely speaking, then meeting her future colleagues at the second one, and shares tactics that work for socially awkward people. We also talk about the Tube Feed Tracker, the web app she built after watching ICU nurses struggle with feed rate math for her medically complex son. It grew to roughly four thousand users and now includes BMI based rate suggestions and a calorie tracker covering seventy verified formulas. Roxy closes with why career switchers cannot go it alone, and why community matters more than any single course. Plus a tiny internet troll lightning round covering course playback speeds, salmon shirtgate, and conference karaoke.

Closed That Tab is back. Erika finally read Richard Cook's How Complex Systems Fail, an 18 point paper Cook wrote with patient safety and medical systems in mind, but one that is frequently discussed in web development and software engineering since the foundational principles apply universally. Erika and Bethany work through what holds up in practice.

Brian Okken, lead engineer at Rohde & Schwarz, creator of the pytest book and course, and author of the new book Lean TDD, joins us to rethink test driven development. His core argument: write tests at the highest level that still makes sense, so you can refactor, restructure, and hand work to an agent without rewriting your suite every time. We dig into why function-level tests with heavy mocking are often harder to write than system-level tests, why the "TDD takes too long" complaint usually comes from testing at the wrong level, and why old rules about test speed no longer hold up on modern machines and CI. The conversation also covers the lean side of Lean TDD: what counts as waste in a test suite, when to delete tests you wrote on the way to a better one, and why a thousand tests is not automatically better than twenty. Brian shares how caring about the whole system rather than just his slice of it changed his career, how he works with AI agents while still reading every line they produce, the stigma around test engineering roles, and what he learned self-publishing a 100 page book and recording the audiobook himself. He closes with advice for newer engineers on large codebases and why everyone is winging it more than you think.