Bad Code Will Never Let You Go

If you are writing code with multiple responsibility, eventually you will lose the control over code and code will put you in trouble.

Reference:

http://www.graffitoid.com/2015/08/solid.html

Single Responsibility Principle

Single Responsibility Principle-Classes with more than a one responsibility should be split  into smaller classes with single responsibility.

Reference:

Wikipedia-https://en.wikipedia.org/wiki/Single_responsibility_principle

SOLID Serious

SOLID Principles 

SOLID is set of programming practices to make your code more adaptive to change.

I would like to post serious of blog posts to make Graffitoid version of SOLID Principle. I believe that understanding and remembering (remembering because we forget the practices when we are in hurry to deliver)  SOLID principles are important in programmers life. Graffitod version will help you to visualize it in a different way.

Part 1:S -Single Responsibility Principle
Part 2:O -Open Closed Principle
Part 3:L- Liskov Substitution Principle
Part 4:I- Interface Segregation
Part 5:D-Dependency Inversion

Reference:
Robert C Martin: http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod
Wikipedia: https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)

How It Works

The Team