I've learned about this book in a hackernews thread where people were sharing good books under 200 pages.
Now, this is the best thing about this book. In under 200p, you can skim through it in a weekend.
Now regarding the content, I'm not quite sure.
Even though most of the advice is great, some of them feel a bit opinionated (using comments everywhere). Others are too obvious (benefits of good naming, etc.).
Another downside is that in my opinion, some of the chapters are lacking a more practical view, staying too theoretical to be useful.
But in general, it's quite a solid book with many good approaches to software design.