Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Which if the SOLID principles introduced by "Uncle Bob" Martin had the largest effect on your day to day coding? Please give details!

share|improve this question

closed as not constructive by Thomas Owens Oct 26 '12 at 18:12

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

All of them, and none of them per se - I started with OO programming about ten years before Uncle Bob's first book came out. ;-)

My favorite principle is DRY = Don't Repeat Yourself. Also called 'normalization'!

share|improve this answer
When I saw a question, first thing what appears in my head was DRY , so I guess its my favorite also – artjom Nov 30 '10 at 9:18
DRY is a good 'un, but it isn't part of uncle Bobs principles. – Mongus Pong Nov 30 '10 at 9:47
@Mongus: SOLID is good, but not comprehensive. – Steven A. Lowe Nov 30 '10 at 14:43
@Steven, I would say the SOLID principles could probably be seen as aspects of the pathway to DRY within an object oriented framework. I don't disagree with you. DRY is my guiding rule. The question was about SOLID principles tho - I was just being picky :) – Mongus Pong Nov 30 '10 at 19:54
@Steven...I am trying to not to sound pedantic here...but the itch is just too bad. SRP and DRY are like apples and pencils - completely different. Sure following SRP can help you to be DRY, but you have to do a lot more than that to be DRY, and you can still be DRY without following SRP. You don't even need to be OO to be DRY. – Mongus Pong Dec 1 '10 at 0:06

S ingle r esponsibility p rinciple.

Whether I'm working a small utility or a large scale service, I like my components to do one thing and to do that thing well. It makes my components easy to test and promotes code reuse.

The rest are important too.

share|improve this answer

I will say ISP and a to a slightly lesser extent SRP. I must clarify that it was much later after I started following these principles that I heard about SOLID. The reason SOLID is so popularis because, like Design patterns, it is summarization of good programming practices that programmers follows through intuition or experience and not an exercise in coining jargons (which I have come to believe is the major side effect of programming)

share|improve this answer

I would say that the largest benefit I had is from preaching SRP to other developers on my team(s).

God objects and 10KLOC classes are a productivity killer even on a small team.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.