Single Responsibility (SOLID Design Principles)

Показать описание

SOLID is an acronym for the first five object-oriented design (OOD) principles by Robert C. Martin (also known as Uncle Bob).

These principles establish practices that lend to developing software with considerations for maintaining and extending as the project grows. Adopting these practices can also contribute to avoiding code smells, refactoring code, and Agile or Adaptive software development.

SOLID stands for:

S - Single-responsiblity Principle
O - Open-closed Principle
L - Liskov Substitution Principle
I - Interface Segregation Principle
D - Dependency Inversion Principle
In this article, you will be introduced to each principle individually to understand how SOLID can help make you a better developer.

Single-Responsibility Principle

The Single-responsibility Principle (SRP) states:

A class should have one and only one reason to change, meaning that a class should have only one job.

For example, consider an application that takes a collection of shapes—circles, and squares—and calculates the sum of the area of all the shapes in the collection...

#solid #singleresponsibility #oop

Рекомендации по теме

Комментарии

You say - AreaCalculator should be only be concerned with some of the areas of provided shapes. What if we rename AreaCalculator to SumCalculatorOutputter and make 2 public methods: JSon and HTML - result would be the same as AreaCalculator.

dariusv

intereting. So class createing html and JSOn outputs does single thing? I never understand how this is calculated :D I would think - JSON is one thing, HTML is another thing, so a class is doing 2 things. Yea, you said "one reason to change" which is bit hard to understand :)

dariusv

And also if we do not need JSON now but only need HTML, so is it really worth to have such small classes with one method? I think if class grows, we then can always extract to new class but while class is small, managable, no problem. Unless we soon expect it to grow, like in comming days or weeks. Otherwise I am not sure if it is worth to have millions of small classes with few lines.

dariusv

You should use less common examples. These examples provide no more information than every other video on this subject.

Laflamablanca

Single Responsibility (SOLID Design Principles)

Single Responsibility Principle Explained - SOLID Design Principles

SOLID Principles: Do You Really Understand Them?

Single Responsibility (SOLID Design Principles)

Low Level Design 105 | Single Responsibility Principle in SOLID | 2022 | System Design

Software Design - Introduction to SOLID Principles in 8 Minutes

SOLID Design Principles with Java Examples | Clean Code and Best Practices | Geekific

SOLID Design Principles Explained in a Nutshell

SOLID - Single Responsibility principle in 3 minutes

SOLID Design Principles in Salesforce - The Single Responsibility Principle

Uncle Bob’s SOLID Principles Made Easy 🍀 - In Python!

Design Patterns: Single Responsibility Principle Explained Practically in C# (The S in SOLID)

Becoming a better developer by using the SOLID design principles by Katerina Trajchevska

Single Responsibility Principle (SOLID) | A single reason to change — Code Walks 006

Uncle Bob SOLID principles

Be A SOLID developer | Design Principles using Java + UML + OOP | Single Responsibility Principle

Learn SOLID Principles with CLEAN CODE Examples

#18 Single Responsibility Principle || SOLID Design Principles

Single Responsibility Principle from Solid Design Principle in OOPs/Java

Solid Programming - No Thanks

Single Responsibility Principle With Simple Example | SRP | SOLID Design Principles

What is Single Responsibility Principle ?

Single Responsibility Principle | SOLID Design Architecture

Introduction to SOLID Design Principles

Single Responsibility Principle in React (Design Patterns)