Tags » Single Responsibility Principle

How to implement Open Closed Principle and 2 other SOLID principles super easy way

Adapting to changes quickly in software development has a nice term called “Agility”. Agility of development depends on the agility of the underline design the development based on. 1,426 more words

Dependency Inversion Principle

Solid Principle: Single Responsibility Principle (SRP)

So, its been quite long I have not been doing any blogging. I thought and I really would wish to start  my blogging with Azure Webjobs series… 738 more words

Refactoring

Coding with Ruby: The Single Responsibility Principle

What is the Single Responsibility Principle (SRP)?

SRP is the practice of classes having one function or responsibility encapsulated within them. All the methods and instances should be as closely aligned to this one function as possible. 203 more words

London

Single responsibility principle

Single Responsibility Principle:

  • a class or module should have one, and only one, reason to change.
  • keep a class focused on a single concern you should refactor the code into a class of its own, When code doesn’t belong in the class that contains it,
  • 894 more words
Ruby

What is SOLID Principle?

SOLID is a five basic principle of OOP and design. It stands for

  • S: Single responsibility Principle
  • O: Open closed principle
  • L: Liskov Substitution
  • I: Interface segregation
  • D: Dependency Inversion.
Design Principle

Implementing Web API Versioning using OWIN

In my previous post "Designing Web API Versioning" I covered some of the design aspects of versioning and in this post I am going to show you how to implement versioning in Web APIs using OWIN. 1,085 more words

Web API