Grokking SOLID Design Principles
The five principles behind maintainable object oriented code, with examples of what violating each one costs later. Short, and it directly improves the code you write tomorrow.
Course
Other
Design Gurus
1 week
Beginner
Subscription
What it covers
Single responsibility, open closed, Liskov substitution, interface segregation and dependency inversion, each shown as a before and after rather than as a definition to memorise.
Why it is worth a week
These principles are quoted constantly and understood rarely. Most engineers can expand the acronym and cannot say what the Liskov substitution principle actually forbids or why it matters. Seeing the failure each principle prevents is what converts it from trivia into judgement.
How to use it
Take a class you find hard to test and identify which principle it violates. Difficulty testing is usually the symptom, and these five are usually the cause.
Best for: engineers in their first few years, and anyone preparing for a low level design round.
Ready to start?
Opens on Design Gurus in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
Follow along
New writing, resources and project ideas land here first.