Nice, I'd been wishing for a "devops" book full of case studies - what situations teams were in and how they handled it. Occasionally you get an engineering blog post, but most of those are just boasting unilaterally about a solution, and not any critical discussion of the problem or the myriad of bandaids most of us have to deal with.
This might be a step in the right direction.