Tags » Single Responsibility Principle

[Fake it ‘til you make it] SOLID OOP - S stands for "Not my fucking job"

You’re knee-deep into your interview now, with your interviewer absolutely wowed by your grasp of the Liskov Substitution Principle. You allow yourself to breathe and think “I’ve got it, this job’s mine”. 892 more words

SOLID

Does DDD promote large Aggregates?

Recently, we had a presentation at my workplace about Domain-Driven Design concepts, given by my team member. He tried to explain the main thoughts behind it and gave some real world examples to make it easier for the spectators to grasp them. 1,279 more words

Domain-Driven Design

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

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