เกี่ยวกับตอนนี้

ภาษาอังกฤษ
สหรัฐอเมริกา

สำเนาบทสนทนา 🔗

ค้นหาตอนที่ผ่านมา

ค้นหาตอนที่ผ่านมาของ Continuous Delivery Office Hours

ตอนอื่นๆ ใน PODCAST นี้

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…
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 &…
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…

CD Office Hours Ep.2: Am I Deployable?

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…

CD Office Hours Ep.3: Branching strategies

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…
ข้อสงวนสิทธิ์: พอดแคสต์และอาร์ตเวิร์คที่ฝังอยู่ในหน้านี้มาจาก Future of Dev ซึ่งเป็นทรัพย์สินของเจ้าของและไม่มีส่วนเกี่ยวข้องหรือรับรองโดย Listen Notes, Inc.