Grokking Design Patterns for Engineers and Managers
The classic object oriented patterns presented with the problem each one solves, so you apply them where they help rather than everywhere. Pattern vocabulary shows up in design rounds and in every code review you will ever have.
Course
Other
Design Gurus
2 to 3 weeks
Intermediate
Subscription
What it covers
The creational, structural and behavioural patterns, each introduced by the problem before the solution, plus honest notes on which ones have been superseded by language features.
The trap it avoids
Design patterns taught badly produce engineers who wrap everything in a factory. Taught well, they are a shared vocabulary for describing a design decision in three words instead of three paragraphs. The distinction is whether you learned the problem or only the structure.
How to use it
For each pattern, find an instance of it in a codebase you already work in. Most patterns are already in your code under different names, and recognising them there is what makes the vocabulary stick.
Best for: engineers preparing for low level design rounds, and anyone who wants their code reviews to be shorter.
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.