Continuous Delivery – Getting to Yes (for our changes)
Nobody likes getting told “no” from a person or, ironically today, a system. As software engineers, our bread and butter depends on getting our ideas into the world, i.e. off our laptop and into some sort of environment where more than us can access — into production. Deploying and delivering software is one large confidence-building exercise; did the features match the expectations? There is a lot of room for human and systemic “no” there. One of the first books I read out of school as a young consultant was Roger Fisher’s and William Ury’s “Getting to Yes: Negotiating Agreement Without Giving In.” Continuous Delivery is as much as automating a “yes” as setting forth what would be a “no.” There are multiple Continuous Delivery methodologies that parallel the book such as “separating people from the problem” aka CD Automation. In the CNCF world, there are over 1200 cards in the CNCF landscape. Each change in each one we leverage can result in a “no.” There are tools out there and practices we can use: Argo, Tekton, WeaveCloud, CodeFresh, and Harness are a few. In this session, we’ll learn what these platforms and processes try to achieve with getting us to a “yes!”
