Design Principles [closed]

Answer 1

SOLID principles and Liskov's pattern, along with Single responsibility pattern.

Answer 2

The most fundamental design pattern should be KISS (keep it simple stupid) Which means that sometimes not using classes for some elements at all it the right solution.

That and CRC(Class, Responsibility, Collaborators) cards (write the card down in your header files, not on actual cards that way they because easy to understand documentation too)

Answer 3

Domain Driven Design is generally a good principle to follow.

Answer 4

Don't forget the Law of Demeter.

Answer 5

Principles Of Object Oriented Class Design (the "SOLID" principles)

• SRP: The Single Responsibility Principle A class should have one, and only one, reason to change.
• OCP: The Open Closed Principle You should be able to extend a classes behavior, without modifying it.
• LSP: The Liskov Substitution Principle Derived classes must be substitutable for their base classes.
• ISP: The Interface Segregation Principle Make fine grained interfaces that are client specific.
• DIP: The Dependency Inversion Principle Depend on abstractions, not on concretions.

Source: http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod

Answer 6

Basically I get away with programming to interfaces. I try to encapsulate that which changes through cases to avoid code duplication and to isolate code into managable (for my brain) chunks. Later, if I need, I can then refactor the code quite easily.