S: Single-Responsibility Principle - Too Big Methods

Before We Begin: What is SOLID and My Initial Thoughts

S: Single-Responsibility Principle - Too Big Methods

Course Content

Intro

01 Before We Begin: What is SOLID and My Initial Thoughts

SOLID Principles: One by One with Examples

02 S: Single-Responsibility Principle - Too Big Methods

03 S: Single-Responsibility Principle - Too Big Controllers

04 O: Open-Closed Principle - Report Formats with New Classes

05 O: Open-Closed Principle - Vendor in Laravel

06 O: Open-Closed Principle - Eloquent Attribute with Salary Calculator

07 L: Liskov Substitution Principle - Type-Hint Everything

08 I: Interface Segregation Principle - Default Laravel Models

09 I: Interface Segregation Principle - Separate Data and Download

10 D: Dependency Inversion Principle - Pass the Parameter as Interface

11 D: Dependency Inversion Principle - Report Interface

Examples in Open-Source Repositories

12 Monica CRM: 4 Principles with Some Potential Improvements

13 Koel Music Service: Useful Services and Kinda Useless Repositories?

14 Spatie Media Library: HasMedia Interface with Trait Implementation

15 Laravel Fortify: Override Views for All Pages

How to Make Your Code SOLID?

16 Tools for Static Analysis to Detect SOLID Violations: Larastan, PHP Insights, PHP Metrics

Other Principles and SOLID Criticism

17 DRY: Blade Components

18 Fowler's Code Smells

19 YAGNI And Premature Optimisation

20 SOLID is Too Old? Introducing SHOC and CUPID

Final Words

21 So How to Apply SOLID in Everyday Coding?