OOP The Good Parts: Message Passing, Duck Typing, Object Composition, and not Inheritance
With traits, structural typing and #akka, #scala is doing this right.
The Single Responsibility Principle - Programmer 97-things
This seems to be in direct conflict with “encapsulate behavior, not just state” and always side with Uncle Bob.
Encapsulate Behavior, not Just State - Programmer 97-things
I love the idea of these simple objects that have all sorts of business relevant methods for state manipulation but I can never seem to get it to work in reality. To do any sort of complex validation the database ends up being involved and if you are using a data access object pattern there is no way too easily reference it in your data objects.
SOLID: Software That Works | .NET Zone
I’ve been reading more and more on SOLID. This seems to be the best, straight forward rundown of it yet, with great motivational posters to boot.