Back Button PHP

SOLID Principles in PHP

SOLID represents a series of guidelines that developers can use to, if done well, simplify and clarify their code. While certainly not laws, understanding these concepts will make you a better developer.

5 episodes
57:12 mins
Start Series
    1. Run Time 12:13 Free

      The most popular of the SOLID design principles, the single responsibility principle dictates that a class should have only one reason to change. To illustrate this a bit more, let's dig into a simple example.

    2. Run Time 13:22

      Open-Closed? Huh? This is one of those principles that developers often skip over. Don't! These techniques are paramount to mature design.

    3. Run Time 9:34

      Coined by Barbara Liskov, this principle states that any implementation of an abstraction (interface) should be substitutable in any place that the abstraction is accepted.

    4. The Interface Segregation Principle states that a client should never be forced to implement an interface that it doesn’t use. As you'll find, this all comes down to knowledge. Learn what I mean by that in this lesson.

    5. There's a common misunderstanding that "dependency inversion" is simply another way to say "dependency injection." However, the two are not the same. So let's dive in and figure this out!

You May Also Enjoy...

Here are some additional series that may be up your alley.

10 Lessons
1:59:19 hrs
7 Lessons
28:25 mins
8 Lessons
1:43:02 hrs

PHP Bits

8 Lessons
31:49 mins
8 Lessons
31:49 mins