Software delivery is a lot like traveling. Less luggage makes for a better experience.

Today I go on record admitting I don't always use TBD, I do sometimes use long-lived branches, and I sometimes even share a branch with another dev.

A group of people with a lot broader experience than I have, come up with a pretty good definition of "Minimum Viable Continuous Delivery".

Continuous Delivery reliably predicts less time spent fixing bugs. How close are you?

In 2022, I can't think of any legitimate reason that a place of business should need to close for a software upgrade.

Can you test your changes in a production-like environment before merging? Here are two ways.

Actually, CI does work for mobile. But Continous Deployment may not.

Joy Ebertz is a Principal Software Engineer at Split. She focuses on the technical vision for the backend team, and she joins me today to talk about some of the obvious, as well as not so obvoius ways in which feature flags can be used on projects of any size.

This week I share the story of a single bit gone wrong back in 2006, which launched my career on a new trajectory of root-cause analysis, continuous improvement, and DevOps.

The gang discusses the dos and don’ts of choosing CI/CD tools.

You've decided GitFlow is totally uncool. But what if you're already using it? How can you break the habit?