OM DETTA AVSNITT

Engelsk
USA

UTSKRIFT 🔗

SÖK TIDIGARE AVSNITT

Sök efter tidigare avsnitt från Continuous Delivery Office Hours.

ANDRA EPISODER I DENNA 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…
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…
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…
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…
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 fr…
Ansvarsfriskrivning: Podcasten och konstverket som är inbäddat på den här sidan är från Future of Dev, som är dess ägares egendom och inte anslutet till eller godkänt av Listen Notes, Inc.