I had it recommended to me once a blog post I’d written on engineering management hit the front page. I bought it and read it based upon that comment. He basic

I had it recommended to me once a blog post I’d written on engineering management hit the front page. I bought it and read it based upon that comment. He basically has some very strong opinions about the seriousness of knowing your domain and systems well. Given the risks inherent in submarine nuclear reactors, he really focuses on deeply knowing your shit, so you can model problems holistically. How practical this advice is in a modern environment of doing more with less and selecting trade offs with less than perfect information is an open question. That being said, if you want to reflect on your own standards for yourself and your work, it’s good.