News for hackers. Stuff that matters.
Re:OO Design Principles Compilation by techiferous on Sunday February 27, 2011 @06:13PM (#2269292)
Notice the number of shoulds. A list of what you should do is like training wheels: useful for beginners but not as much for the advanced.

Instead of thinking in shoulds I like to think in terms of causes and effects. If you don't follow the law of demeter then these will be the effects. Then the programmer realizes they have a choice: even though the law of demeter usually brings about desirable consequences, maybe in a particular situation the effects of not following the law of demeter bring about the better set of consequences.

Thinking in terms of causes and effects also loosens potential dogma.

Re:OO Design Principles Compilation by extension on Sunday February 27, 2011 @06:46PM (#2269368)
Someone please add this to the top of the list.

There is little value in following programming rules that you don't understand.

Re:OO Design Principles Compilation by fleitz on Sunday February 27, 2011 @07:10PM (#2269409)
Agreed. Most of software 'methodology' is really software ideology. It's just cargo cult programming. For me the key consideration in building software is whether it produces more money than it consumes.