Comment by yawboakye
2 years ago
i read this book. no, i studied it but found it less about philosophy of software design and more about how to deal with the current state of affairs. it does a good job here, in my opinion. but as a work of philosophy it undersells. one criteria is can a non-programmer study and have any idea what software design should be about? in my experience, the answer is no. a philosophy of software design shouldn’t necessarily target software designers/engineers. amazing book, wrong title.
An honest book would explain the trade-offs instead of say "design X is always better than Y". Context and domain matter. One-size-fits-all is wrong.
Have you read the book? I felt it did that quite well.
The overall pattern really seemed to be “I think we should do X because Y. This falls apart in the face of Z, so don’t do it there.”
That said, it’s been a couple years since I read it so I may be misremembering.