Podcast: Continuous Delivery Office Hours

Continuous Delivery Office Hours

CD Office Hours Ep.2: Am I Deployable?

Play Episode Pause Episode

Mute/Unmute Episode Rewind 10 Seconds 1x Fast Forward 30 seconds

00:00 / 00:36:38

RSS Feed

Share

Link

Embed

To ensure software is deployable, teams must shift from manual testing to automated pipelines. Automation provides immediate feedback, captures institutional knowledge, and reduces long-term costs. Strategies like the Strangler Pattern help modernize legacy code for greater reliability.

Listen to find out more about:

• How deployability depends on continuous automated verification
• How automation is a long-term crucial investment
• Strategies for modernizing legacy code
• How automated tests are a form of living documentation
• Why leadership buy-in and cultural alignment is a necessary pre-condition

Episode map

Watch the video

Continuous Delivery Office Hours

CD Office Hours Ep.1: Prioritizing Continuous Delivery

Play Episode Pause Episode

Mute/Unmute Episode Rewind 10 Seconds 1x Fast Forward 30 seconds

00:00 / 00:23:37

RSS Feed

Share

Link

Embed

Tony Kelly hosts our first episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton.

In this episode of Continuous Delivery Office Hours, we ponder why prioritizing Continuous Delivery (CD) is essential for managing risk. We challenge the common instinct to reduce deployment frequency after failures, using a dentist analogy to explain how delaying deployments increases pain and risk by allowing unchecked changes to accumulate.

We advocate decoupling “deployments” (moving code) from “releases” (exposing features) using trunk-based development and feature toggles, which lets you test safely in production and avoid the deadlocks of complex dependency management.

Listen now to discover:

• The dentist paradox
• Guts on the table
• The dog and biscuit
• Steering with your knees

Episode details

Watch the video