Common break-even calculations for TDD are wrong when experienced TDD devs are involved becuase TDD makes development faster.

Joel Clermont, host of the No Compromises podcast, shares his wisdom on the topic of good digital hygiene, as it relates to development projects, particularly the bits that aren't software. Have you ever joined a team with poor documentation? With third-party credentials scattered all over the place?

Merge a minimum of one PR each day. Make small PRs. Don't worry if the feature is incomplete, only that each PR works.

I love the term "Full-Cycle Developer", as I think it helps encapsulate the goal of the U-Shaped Cell.

Guest Goerge Stocker cuts through the often polarizing debate about Test-Driven Development (TDD) and offers his view on when the practice does and DOES NOT make sense, based on technology as well as human factors which are often overlooked.

In this episode, I talk with Peter Morlion about his love for fixing and improving legacy code, what legacy code is, how we can detect it, and what to do about it when we're faced with it.

Most education focuses on how to code, but this is only a small part of becoming a productive software developer.

A good developer will reproduce a bug in a test environment, fix it there, then deploy to production.

The Mikado Method is a system of quick, iterative experimentation for rapid and safe code changes.

Software, like surgery, should be a last resort, when all other options have been exhausted.

The Toyota Production System's U-Shaped Cell is a favorite DevOps analogy: Put all the tools within reach of a single developer.