Seconding this. It's an important book for all kinds of design
I would also recommend "Clean Code: A Handbook of Agile Software Craftsmanship" by Robert C. Martin. It focuses on crafting higher quality code, which is the property of it not only running well, but being easy to understand and to work on
I personally don't like Clean Code, but understand that a lot of people I respect do. I do want to throw Clean Architecture into the ring though since we're in the topic.
That book is a top three software book for me. It made me understand why OO is a thing and what concepts I should pretty much always use from that ecosystem.
The concept of interfaces (not just the programming construct, but the general idea) was massive and it changed my view on the testability of code.
Martin has some other good stuff related to professionalism as a programmer. He has a few talks and The Clean Coder and those are absolutely worth it as well.
While the criticism is valid, I think it misses the points of the book. It's worth reading both but the book definitely has helpful perspectives that eclipse what's mentioned on that webpage
https://www.goodreads.com/en/book/show/840