Continuous Deployment is about Continuous Management.

Practices that create shorter feedback loops help gamify the software creation process, and more frequent dopamine releases.

Some projects obviously need automated builds. Others obviously don't. Where do you draw the line?

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

Olaf Molenveld joins me to explain the concept of Progressive Delivery, when it makes sense, and what homework every team should do before getting started.

Even if we reduce defects to, one per year, if repar takes days, any gain is lost.

How can we discover conflicting changes on separate branches as early as possible?

“Whether a human is involved in pressing the deploy button or not, you are going to deploy a bad update eventually.”

"Grant me strength to accept changes a week before a release" — But why aren't we using Continuous Delivery?

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

How to use feature flags if you don't have feature flags.