View screencasts by curated topics.
Dive into the archive of all episodes.
Mocks are a handy tool for ...
Setup your development environment.
Configure your production server.
Learn how to modify production to run websockets.
In this series, we'll explain the SOLID principles using real-world examples as best we can so you can see how design patterns and principles can affect your code making it easier to read, understand, test, and maintain.
A class should have only a single responsibility
Software entities should be open for extension but closed for modification
Subclasses should add to a base classes behavior, not replace it
The Interface Segregation Principle states that no client should be forced to depend on methods it does not use
Abstractions should not depend upon details. Details should depend upon abstractions