adamcath

Disclosure: the author is a close friend of mine. I helped him with feedback on some parts of the book. And I haven't read the whole thing yet.

Nonetheless, I'm confident that for newer engineers, this book will save you years of learning about the "real world" the hard way. Even if our technical education is top notch, there's so much more to being a great engineer who can thrive in any environment - from BigCo, where there are a thousand unwritten rules - to startup, where you have to figure everything out yourself.

And even for experienced engineers, it may help you reflect on what you've learned and consolidate your ideas more clearly.

The best book I found in this area was The Clean Coder, but it was mostly for the main thesis - that we should strive to be professionals, just like a "real things" engineer or doctor - the details were not terribly memorable. DH's book takes it to the next level with concrete and immediately applicable advice like "unblock yourself", "improve your writing", and "maintenance is for suckers".

How did you get all the services into docker, process-wise/socially/politically? Is your place really small? Or did every team buy into the idea? Or did someone dockerize everyone else's services?

That is a cool idea. It never occurred to me to make it interactive. How would you imagine that interactive mode would work?

Does anyone know the math behind exactly how wrong the averaged percentiles are? My dim understanding of stats makes me think the central limit theorem is at play here; the averaged p99 values will tend towards a normal distribution, which is obviously wrong. Would love to be schooled on it.