ÜBER DIESE EPISODE
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 […]
Englisch
Vereinigte Staaten
TRANSKRIPT 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
VERGANGENE FOLGEN SUCHEN
Vorhandene Folgen von Continuous Delivery Office Hours durchsuchen.
WEITERE EPISODEN IN DIESEM PODCAST
While application code deployments have become highly automated and disciplined, database changes often remain manual, “folksy,” and prone to causing messy environment drift. Find out why databases require a uniquely cautious approach due to the severe risks of data loss and the impossi…
In this episode of Continuous Delivery Office Hours, Tony Kelly, Bob Walker, and Steve Fenton discuss the purpose and common pitfalls of software change approvals. They argue that strict, manual change approval processes are often just a reflex to past organizational trauma and an attempt to have &…
Your system’s architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a sticky mess. This episode looks at whether choosing a monolith or microservices fundamentally changes the crucial properties of your architecture. Listen to…
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 f…
Your branching strategy can support Continuous Delivery, or make it an impossible goal. Teams should assess the impact of how they branch on their ability to deliver software at all times, and that means there are some branching techniques that make software delivery more like walking in the dark t…
Rechtliche Hinweise: Der auf dieser Seite eingebettete Podcast und das Bildmaterial stammen von Future of Dev, das Eigentum seines Eigentümers ist und nicht mit Listen Notes, Inc. verbunden ist oder von diesen unterstützt wird.
BEARBEITEN
Vielen Dank, dass Sie uns helfen, die Podcast-Datenbank auf dem neuesten Stand zu halten.
