What are best practices for using git hooks for developer productivity?

Avoid a big up-front investment in automation by building it piece by piece, as needed.

What's preventing you from releasing on demand, in 20 minutes or less?

What should you do with broken tests on an old project? Delete them. Probably.

Bryan Finster is a co-creator of Minimum Viable Continuous Delivery, and in this episode we talk about how this concept was born, what problems it aims to address, and how you can use it on your team to improve your continuous delivery.

The panel jumps in and discusses the Minimum Viable Continuous Deployment from the manifesto on the web and discuss where they agree and disagree with the requirements listed there and clarify some of the ideas in the document.

Over the 12 months I worked on this project, there were two instances in which deployments were blocked for more than a week.

Just as software delivery can be separated from deployment, feature deployment can be separated from release.

CD takes the concept of a CI pipeline to its logical conclusion. But that doesn't mean you have to implement a complete CI pipeline first.

Does your team face code freezes? What's preventing you from using trunk-based development and continuous integration to thaw your code once and for all?

By working in smaller iterations, we don't just re-organize our work, we actually reduce the amount of work we do.