Thanks for laying this out so clearly. The whole time you were going over the Liskov Substitution Principle I was expecting you to suggest type-hinting the array structure using DocBlock and static analysis tools! That's what our team uses to enforce this programmatically.
I can't tell you how disappointing it is to find such a clear and thorough video aimed at programmers working actively in PHP / Laravel to then find out you don't have other videos on your channel…
That's one of the best explanations of SOLID I've seen in a long time. Maybe it's because the examples were created using a familiar environment, but regardless, good job!
Just a minor correction. The D in solid refers to Dependency Inversion. But yes, you're correct that it means that you should depend upon abstractions rather than concretions. Great video :)
Quality content. Subscribed! You mentioned you have a strong opinion on the repository pattern; do you have any video or article outlining your opinions?
There's input validation and there's business-related validation. Limiting the string length, ensuring price is numeric, or restricting the image size is typically not part of the business logic.
Thanks for laying this out so clearly. The whole time you were going over the Liskov Substitution Principle I was expecting you to suggest type-hinting the array structure using DocBlock and static analysis tools! That's what our team uses to enforce this programmatically.
I can't tell you how disappointing it is to find such a clear and thorough video aimed at programmers working actively in PHP / Laravel to then find out you don't have other videos on your channel…
That's one of the best explanations of SOLID I've seen in a long time. Maybe it's because the examples were created using a familiar environment, but regardless, good job!
Just a minor correction. The D in solid refers to Dependency Inversion. But yes, you're correct that it means that you should depend upon abstractions rather than concretions. Great video :)
Hey Taylor, are you looking for a job as a laravel dev? If yes, any way to contact you?
Quality content. Subscribed! You mentioned you have a strong opinion on the repository pattern; do you have any video or article outlining your opinions?
This was a great breakdown and one that I would love to share with my dev team.
Thank you sir.. I gained knowledge and tricks here. I will work more on understanding and adhere to SOLID principle
the things that i noticed sometimes with the way laravel is built is that sometimes added too much extra abstractization ends up making spaghetti code
Thank you for the great video on SOLID. Please do more videos.
Nice video, you should make more, great teaching style, cheers 👊🏾
Great explanation. Subscribed!
Nice video. Any plan for more education videos like this in future?
i got error using the same logic. The purchase method is confusing in Open/Closed Principle
yeah me too
For SRP validation should be done in the productService as well. That is business logic and not related to the HTTP cycle.
There's input validation and there's business-related validation. Limiting the string length, ensuring price is numeric, or restricting the image size is typically not part of the business logic.
that's why you have the request classes, for validation
Thanks 🙏
SOLID video 🤘