Single Responsibility Principle Explained - SOLID Design Principles

🚨 IMPORTANT:

1 Year Free Hosting: https://www.atlantic.net/webdevsimpli...
Use code KYLE for an additional $50


Writing clean code is tough, and is one of the largest differences between junior and senior developers. One way that you can quickly improve your code and start writing well designed code now is to implement the single responsibility principle. This principle is part of the SOLID design principles and is, in my opinion, the most important rule of SOLID. This is because it is easy to implement and test for while still being incredibly useful in terms of making your code cleaner.

The main idea of the single responsibility principle is that every class/function/module/section of your code should have only one responsibility. This means that the code should only have one single reason to change. If there are two different reasons for the code to change, or if it does two distinctly different things then it is in violation of this principle and is potentially poorly designed code.

Most likely you have written tons of code in violation of this principle, I know I have, but hopefully this video will help introduce you to why this principle is so good at making your code clean and maintainable.


🧠 Concepts Covered:

- What the single responsibility principle is
- Why the single responsibility principle is important
- How to use the single responsibility principle
- How to spot violations of the single responsibility principle


🌎 Find Me Here:

My Blog: https://blog.webdevsimplified.com
My Courses: https://courses.webdevsimplified.com
Patreon:   / webdevsimplified  
Twitter:   / devsimplified  
Discord:   / discord  
GitHub: https://github.com/WebDevSimplified
CodePen: https://codepen.io/WebDevSimplified


#SOLID #WDS #SingleResponsibilityPriniciple