The notes of Justin Abrahms

Recently updated

OReilly_Continuous_Delivery_In_The_Wild-diff

Feb 16, 20264 min read

Reading Plan: Continuous Delivery in the Wild — Pete Hodgson

Generated by book-diff

Summary

CategoryCount%
Novel217%
Depth Gap1083%
Review00%
Total chunks12

Thresholds: novel < 0.5, review >= 0.65

High Priority: Novel Content

These sections have low similarity to anything in your vault.

pp.1-6 (score: 0.48)

Suggested note: Continuous Delivery Principles

Compliments of REPORT Continuous Delivery in the Wild Pete Hodgson Skip the hotfixes and rollbacks with Split’s Feature Delivery Platform. Pete Ho…

Nearest vault note: Continuous Delivery at Amazon (0.48)

Chapter 4. Deployment and Release > Moving Fast with Safety — pp.32-33 (score: 0.48)

Suggested note: Correlating Changes with System Impact

In order to figure out whether a change has a negative impact an engineer needs to be able to correlate the observed impact (say, an increase in error…

Nearest vault note: Using CHAOSS to measure risk in your portfolio (0.48)

Medium Priority: Depth Gaps

You have notes on these topics, but the book goes deeper.

Chapter 4. Deployment and Release > Coordinating Production Changes — pp.28-29 (score: 0.51)

1 I assume that the Release Bus naming is a play on the traditional Release Train approach, where an extremely large batch of changes accumulates over…

Chapter 3. Running an Integrated System > Testing Changes Prior to Merge — pp.22-24 (score: 0.55)

1 The nomenclature for environments is rather inconsistent across organizations. I’ve typically seen the type of environment I’m referring to here as …

Chapter 2. Branch Management and Code Review > Reducing Batch Size — pp.19-21 (score: 0.55)

Rather than releasing a feature as one large code change, teams spend time breaking a feature down into a set of smaller changes. These changes are al…

Chapter 3. Running an Integrated System > … > Overriding Service Versions in Staging — pp.25-27 (score: 0.55)

then manage them similarly to the personal dev environments described above. With this approach, environments are automatically torn down every night…

Chapter 2. Branch Management and Code Review > Minimal Branches — pp.14-15 (score: 0.59)

That pull request typically also serves as a mechanism for coordinat‐ ing code review. Once a change has been approved it is merged into master. Parti…

Chapter 1. Introduction > The Path to Production — pp.10-13 (score: 0.63)

1 Going forward, I’ll use “master” as a shorthand for the main development branch where a team integrates their work, since that’s the most common nom…

Chapter 4. Deployment and Release > Incremental Deployment — pp.30-31 (score: 0.63)

2 Accelerate, Chapter 2. • Performing data management tasks in an environment (such as reseeding test data or importing scrubbed production data) • Re…

Chapter 2. Branch Management and Code Review > Code Review — pp.16-18 (score: 0.64)

traditional release branch approach, there is often a series of manual steps involved in a production release—cut a branch, update config‐ uration fil…

Chapter 5. Summary > Two Modes of Continuous Delivery — pp.34-36 (score: 0.69)

make a distinction between their Continuous Integration system and their Continuous Delivery infrastructure, where their Continu‐ ous Integration syst…

Chapter 1. Introduction > What is Continuous Delivery? — pp.7-9 (score: 0.78)

CHAPTER 1 Introduction Software companies are under constant pressure to deliver features to their users faster, while simultaneously maintaining (or …

Score Distribution

Score Distribution (top similarity per book chunk):

  0.5 | ######################################## (5)
  0.6 | ######################################## (5)
  0.7 | ######## (1)
  0.8 | ######## (1)

Graph View

Backlinks

  • No backlinks found