i had high hopes for this book since the authors have been very influential for me, especially gene kim - i've listened to every episode of the idealcast and follow anything he works on.

On page 8 i felt a keen sense of disappointment when the book stated that it would be focusing on lead time to deploy (or similar), as that's only one facet of DevOps. I was worried that it was going to just be about CICD, which seemed out of character, given how much Gene focuses on organizational health, structure and dynamics, leadership, etc.

That fear passed very quickly in the following pages when I saw what they were doing - it isn't only focusing on shipping faster, it's about *all* the things you need to do before you can deliver value quickly, safely, and sustainably.

This includes value stream thinking, cross functional teams, testers embedded with teams and acting as enablers, shifting compliance and security left, reducing batch size, building psychological safety, measuring team health (eNPS, SPACE, etc), identifying types of waste (Making Work Visible is also good for this), types of work (flow framework), OKRs, coaching katas, fast bidirectional feedback, reducing planning overhead and coordination overhead, feature flags, dark launches, A/B testing, Gemba walks, non-functional requirements (the ilities), elevating the improvement of daily work over the work itself, and a discussion of trunk-based work vs feature branches (I prefer short-lived feature branches that are continually updated from main)

I've read all of these subjects before, but having them all as part of a single narrative was valuable for collecting my thoughts.