Continuous Delivery Get Real: Tips, Tricks & Basics

What is Continuous Delivery? And find out what happens when teams "Get Real" about CD. Continuous delivery is when you take that shared branch (master/main) and can push it to production safely and quickly. The key distinctions are that it should be fast and automated to get quick feedback and eliminate the chances of human error. We want to make the process of pushing to production “boring,” so we can focus our attention on adding value, not triaging the deployment. Feature flags enable continuous delivery by allowing the teams to release the feature to their end-users when it is ready and have a kill switch if something goes wrong. Author of "Continuous Delivery in the Wild" Pete Hodgson, and CD evangelist Dave Karow "step into the confessional" to share their real world experiences with Continuous Delivery. Speaking in-depth with engineering teams of all shapes, sizes, and levels of sophistication on their paths to production, Pete will share his learnings and discoveries on: - Continuous Deployment - understanding the principles behind the practice. - The underlying value for trunk-based development. Why it's good for some teams and not others. - Guiding principles to help you navigate Continuous Delivery. - Best practices and (hard) lessons learned from the field. You should watch, if you and your team are under constant pressure to deliver features faster, and better.