SOLID Design Principles Made Easy

Let's take a deep dive into the SOLID principles of programming and see how you can implement it in your own coding projects.
►Try CodeCrafters with 40% off! app.codecrafters.io/join?via=...
0:00 How to code fast and without bugs
0:29 What is SOLID programming principles?
0:42 What is the Single Responsibility principle?
1:30 What is the Open-Closed principle?
2:22 What is Liskov's Substitution principle?
3:05 What is the interface segregation principle?
3:40 What is the dependency inversion principle?
--------
GEAR:
► Microphone: amzn.to/3VjSIdL
► Keyboard: amzn.to/499YwtP
► Mouse: amzn.to/3TAlTIm
► Monitor: amzn.to/3Tyjrlv
► GPU: amzn.to/43fgfyB
► CPU: amzn.to/3wY4j8k
If you buy and have any questions about the equipment, feel free to comment or DM me.
--------
♫ Music provided by Epidemic Sound: share.epidemicsound.com/2g7gqr ♫

[@mitheace]

I think you got the SRP wrong, it states that any module should only have one reason to change, where RCM clarifies that this single reason is a single actor. So modules should only get changes requested by one actor and these changes can only be requested by one actor. The responsibility part in SRP refers to the actor, not the module.

[@Yvngsick]

I Agree, Uncle Bob describes this in his book. It's not about only doing one thing, it's about a single actor.

[@Mates15864]

Nice and halpfull video. Thank you.

[@carriocode]

Glad it was helpful!

[@xCookiee]

Nice video

[@the_infinity_snake]

2:24 The example provided doesn't even match the principle at all,
there's no class A or B in the example,
therefore there's nothing related to "replace B with A" (or "replace base class with sub class") in the example at all.
Is it a mistake of choosing the right example?

[@banelethabede4871]

Great vid man , subscribe ++;