Starting in a rigid, process-heavy dev shop where a typo fix required presidential-level approvals, Austin shares how years of stagnation, big batch releases, and public demo disasters (including rogue robots) led him to ask the big question: What if we actually did Extreme Programming all the way—no compromises?

This episode digs into:

- Why doing half of XP might be worse than doing none

- The hidden cost of tolerating just “one bug”

- What daily delivery and value-first thinking really look like in practice

- Experiments on how to survive (and thrive) when your dev culture thinks you’re “too extreme”

- The real tradeoffs of turning XP, TDD, and refactoring up to volume level 11

- When agile and XP becomes a “cargo cult”

- Lessons from being one of the lone voice for clean code in an organization stuck in the middle

Alongside co-host Chris Lucian, Austin reflects on the resistance many developers face when advocating for full adoption of XP practices—like pair and mob programming, evolutionary design, continuous delivery (CD), test driven development (TDD), and bug-free codebases. They also explore how to escape local optima by introducing meaningful “mutations” to your dev environment and culture.

Whether you're a software engineer tired of firefighting and regressions, a team lead wondering why your “agile” isn’t working, or a practitioner curious about what it means to really commit to Extreme Programming, this conversation pulls no punches.

👍 Like the episode? Hit the thumbs up, drop a comment, and share with someone who’s still debating whether TDD is “worth it.”

Video and Show Notes: https://youtu.be/AKXRGmSYgWs