Yes. The book is dense. At over 600 pages, it is not a weekend read. It is a reference manual. You will likely read the section relevant to your current struggle (e.g., "How to conduct a post-mortem") and put it down.
Most of us think our job is to write code that machines understand. Orosz argues our primary job is to write code humans can understand, maintain, and safely change. He dedicates significant space to Communication —not just via comments, but via architecture decision records (ADRs), RFCs, and even how you phrase your pull request descriptions. The Software Engineer-s Guidebook
How do you navigate a politically charged post-mortem? How do you say “no” to a product manager without getting fired? How do you grow from a Senior who just codes to a Staff Engineer who multiplies the team’s output? It is a reference manual