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.

5 ways smaller software releases can impact your business

Adrian Stanek, of Bits in Motion, joins me to relate his success story of transforming his organization's software development process via baby steps.

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?

Not everyone feels the need for your solutions. That's okay. You don't need to convince them.

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.

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.

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