The Process

Scrum Plus Extreme Programming Practices-Adding Extreme practices to Scrum will improve the quality of deliverable. It is easy to follow scrum difficult to follow programming practices. 

Reference:

Scrum - https://en.wikipedia.org/wiki/Scrum_(software_development)

Extreme -https://en.wikipedia.org/wiki/Extreme_programming_practices

Complexity Visualized

Dependency Injection

Dependency Injection:The Processor is dealing with  hats,the hats represents the interface. the composer (example DI containers) is providing the real implementation before calling the processor

Reference

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

Interface Segregation Principle

Interface Segregation: Split the large interface into smaller units based upon clients requirements and architectural requirements.

Reference:

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

Liskov Substitution Principle

Liskov Substitution Principle: When you are creating derived class it should  honor the base relationship with clients.

Reference:

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

Open Closed Principle

Open Closed Principle-Do not allow future changes to existing classes and assemblies. If there is a change required in future, create new code that can extend the existing code.

Reference:

Wikipedia-https://en.wikipedia.org/wiki/Open/closed_principle

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