Grokking Continuous Delivery (Continuous delivery) (Filed under DevEx)

Grokking Continuous Delivery (Continuous delivery) (Rubric #DevEx)

One of the books I read on New Year's Eve was Google's Christie Wilson, a book about modern approaches to continuous delivery. I’m quite cautious about the books in the Grokking series, but then I was bribed that the opening speech was written by as many as two cool engineers who definitely know how to engineering.

• Jez Humble.He has co-authored the books Continuous Delivery, Devops Handbook, Accerate. (I've told you before. first and third booklet)
• Eric Brewer, which formulated the CAP theorem (me I already told you. about)Google Spanner and now VP Infrastructure & Google Fellow Both of these esteemed gentlemen spoke very well of the book in their opening remarks, so I was looking forward to an interesting reading... and it did. But the interest was not due to rocket science approaches, but rather how Christie literally explained from the basics what software development looks like and why you need continuous integration, continuous delivery and how it differs from continuous deployment.

In fact, in a book. 4 parts, 13 chapters 2 It's an application that reminds me of comics -- many chapters deal with the almost real problems of fictional companies like Cat Picture, Super Game Console, Ice Cream for All, CoinExCompare, and so on. This allows the author to demonstrate the evolutionary development of approaches to engineering processes, rather than immediately showing the perfect picture. By the way, the table of contents can already understand how the logic of the narrative is built.

Part 1: Introducing continuous delivery Chapter 1: Welcome to Grokking Continuous Delivery Chapter 2: A basic pipeline Part 2: Keeping software in a deliverable state Chapter 3: Version control is the only way to roll Chapter 4: Use linting effectively Chapter 5: Dealing with noisy tests Chapter 6: Speeding up slow test suites Chapter 7: Give the right signals at the right times Part 3: Making delivery easy Chapter 8: Easy delivery starts with version control Chapter 9: Building securely and reliably Chapter 10: Deploying confidently Part 4: CD design Chapter 11: Starter packs: From zero to CD Chapter 12: Scripts are code, too Chapter 13: Pipeline design

It is important to note that Christie

1. Try not to get attached to CI/CD tools (For this purpose, there is the first appendix, which considers their capabilities.)
2. Provides instructions for setting up piplins for both green-field and brown-field projects
3. Focuses on best practices: VCS as a source of truth, secure deployment using automation, using Pipeline steps to get the right signals about software readiness for deployment, tracking the quality of the delivery process using DORA metrics (More about them in the book Accelerate, which I described in three parts. 1, 2 and 3)

In general, despite my deep immersion in the subject of the book, it even brought me new knowledge and also systematized understanding. I would have loved to read it at the beginning of my career to reduce the number of rakes I had to go through myself:) So I highly recommend it for those who are now starting their way into IT - it is better to get acquainted with the theory of what engineering processes should look like from the book than try to come to them in practice. This is a shortcut to becoming a better engineer.

P.S. The book in Russian was published in the publishing house "Peter" and in my opinion it was translated quite well:)

#Devops #Management #Leadership #Processes #SRE #Software #Devops #Architecture #SoftwareDevelopment