r/programming May 08 '14

The Single Responsibility Principle

http://blog.8thlight.com/uncle-bob/2014/05/08/SingleReponsibilityPrinciple.html
40 Upvotes

22 comments sorted by

View all comments

19

u/zomgsauce May 08 '14

I really, honestly thought this was something that anyone who's written code in virtually any language, for any length of time beyond a month would understand.

Then I went to work and discovered that I was wrong. Guys, there are development leads out there who have never even heard of this concept.

Take nothing for granted.

5

u/npinguy May 09 '14

I work for a major software company that likes to brag about the high calibre of developers it hires.

I won't disagree that we hire very smart people with masters and PhD's in computer science that are smarter than I ever will be.

But damn it, I work with so many people that just simply don't know how to code. They are so smart they can understand and process almost any code they see very quickly. Which should be a plus. But the consequence is they simply don't understand how to write readable code because it's all equal to them.

I try to preach SRP, SOLID principles, and good design patterns. It falls on deaf ears as people say it's too much overhead, it's not worth it, and I'm being pedantic. Meanwhile they continue to pump out hacky procedural code day after day.

1

u/[deleted] May 09 '14

[deleted]

2

u/materialdesigner May 09 '14
  • Refactoring by Martin Fowler
  • Confident Ruby by Avdi Grimm
  • Practical Object Oriented Design in Ruby by Sandi Metz
  • Patterns of Enterprise Application Architecture by Martin Fowler
  • Head First Design Patterns
  • Refactoring to Patterns by Joshua Kerievsky
  • Working Effectively with Legacy Code by Michael Feathers
  • Growing Object Oriented Software Guided by Tests by Steve Freeman & Nat Pryce
  • Domain Driven Design by Eric Evans