No BS SOLID Principles

Подписаться 17 тыс.

Просмотров 2,6 тыс.

50% 1

SOLID principles ain't easy to understand. They are worded in a way which feels ambiguous and confusing. So I created this RU-vid video in order to help you understand what they really mean and what problems they solve or prevent.
🆓 Join garyclarke.tech for course DISCOUNTS and your FREE Docker + PHP course (worth $49)
www.garyclarke...
Here are the repos if you want to download and follow along
github.com/Gar...
👇 Follow me on Social Media:
Twitter: / garyclarketech
Linkedin: / garyclarketech
💕Show support:
www.paypal.com...

Опубликовано:

22 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 23

@bpdkuikel 4 месяца назад

I must thank you for your amazing efforts in taking PHP to general people and creating lots of awareness. 🎉🎉🎉

@GaryClarkeTech 4 месяца назад

Love the kind words!

@jorditrigo9569 4 месяца назад

Many thanks for sharing your knowledge, Gary!

@GaryClarkeTech 4 месяца назад

My pleasure! Thanks for watching!

@Kogemate 4 месяца назад

Great video!!! Everybody who want more durable code should understand these concept.

@GaryClarkeTech 4 месяца назад

Thanks very much!

@astev52 4 месяца назад

Love your work!

@GaryClarkeTech 4 месяца назад

Glad you enjoy it!

@kokokodev 4 дня назад

Coooll❤❤

@thenightwolf224 4 месяца назад

Amazing Video Buddy Keep Going ❤🔥

@GaryClarkeTech 4 месяца назад

Thanks a lot...appreaciated!

@commanderbensisko 4 месяца назад

Hi Gary. I'm just curious why you didn't make SmsDispatcher and Mailer inherit from Notifier and then use a type of Notifier in your code ?

@GaryClarkeTech 4 месяца назад

A Notifier interface or abstract Notifier class would be the best solution but I didn't want to start delving into dependency inversion in the SRP example...it might have become a distraction.

@ta-mas 3 месяца назад

Hello Gary, Great video, it was really really helpful! At the ISP part, let's say not just the archiver needs to read the file to do an operation on it. How should I handle that? Maybe break the interface into even smaller parts, so I have a FileReaderInterface a FileArchiverInterface and an Interface for my other operation that I want to imeplement? Thank you for the amazing content!!

@GaryClarkeTech 3 месяца назад

Cheers for the kind words... Yes just break it up and implement as many interfaces as you need

@BarMineL 4 месяца назад

This is what I need

@Kogemate 4 месяца назад

For the first example, instead of encapsulation, I would use an interface. And only if the class that I am trying to inject does not implements the interface (like an open source class), I would create this class. Actually, it is a classic design pattern. Globally, it is better to rely on interface which is better than abstraction which is better than concrete class. :)

@GaryClarkeTech 4 месяца назад

You're right..but I didn't want to delve into dependency inversion before I got to it..it might have become a distraction.

@Kogemate 4 месяца назад

@@GaryClarkeTech You were actually right not to do it, too much complexity for nothing. BTW, I learned everything about these concept from Miško Hevery (he was Mr Writing-testable-code evangelist at Google). If you google his name, you will find amazing pdfs and yt videos. Lots of tips. As it is a little old, we can see what aged well (almost everything). Take care.

@dandan-js2ir 3 месяца назад

Hi. Great video! One question though regarding Open/Close principle. How to deal with vendor/ directory classes that does not implement an interface? Let's say there is a x package in vendor directory, and that package has a regular class that performs some task (without implementing any interface nor extending an abstract class). How to add Decorator pattern in such case? Thank you and cheers!

@GaryClarkeTech 3 месяца назад

That gets a bit more complex. If you need its functionality you can inject it as a dependency into your own class which does implement the interface. But try to avoid putting square pegs in round holes if it's going to cause more problems than it solves.

@dandan-js2ir 3 месяца назад

@@GaryClarkeTech Thank you for response!