Just recommended to a mentee of mine yesterday referring to it as "one of the best software books in the past few years". Weird coincidence. It really is good, but not super actionable by a lot of engineers since they aren't in a position where they need distributed data or message queues or other interesting tech.
It's very helpful for understanding the software many of us use on a daily basis though, which is extremely important. That sort of knowledge helps you evaluate when different solutions are appropriate, what their shortcomings and strengths are, and to understand why those shortcomings and strengths are there in the first place.
A lot of it is things that could be explained individually, but there's really something to be said for holistic views on a topic.
