I am just in the middle of the book but so far I also have mixed feelings:
+ thoughts on complexity and how constant addition of new features adds to complexity
+ deep vs. shallow modules but at the same time...
- "..classitis": author criticizes the use of many small classes and functions/methods while I think form my experience SOLID principles are there for a reason- every method/class should have one purpose only.
- which leads me straight to my second point of critique so far: nomenclature. for several ideas exist established names already that are not used in the book.
>-"..classitis": author criticizes the use of many small classes and functions/methods while I think form my experience SOLID principles are there for a reason- every method/class should have one purpose only.
I don't understand how you can be so confident that SOLID means you should have many small classes and functions/methods. The question of when we should carve off a piece of reality (natural or artificial) and call it one thing, or say that it does one thing, is an ancient philosophical question with no single right or easy answer.
+ thoughts on complexity and how constant addition of new features adds to complexity + deep vs. shallow modules but at the same time...
- "..classitis": author criticizes the use of many small classes and functions/methods while I think form my experience SOLID principles are there for a reason- every method/class should have one purpose only.
- which leads me straight to my second point of critique so far: nomenclature. for several ideas exist established names already that are not used in the book.