Grokking Design Patterns for Engineers and Managers

It is a complete tour of the 22 classic design patterns, one lesson each, grouped into creational, structural, and behavioral families. Every pattern is introduced with a real-world example, then its structure as a diagram, then an implementation in code, then where it is applied and what it costs you.

Engineers preparing for low level design or object oriented design rounds, developers who keep meeting these names in code reviews and pull requests, and tech leads and managers who need to evaluate a design somebody else proposed. The manager audience is deliberate: the pros and cons material is as useful for judging a design as for producing one.

All 22. Creational: singleton, factory method, abstract factory, builder, prototype. Structural: adapter, bridge, composite, decorator, facade, flyweight, proxy. Behavioral: chain of responsibility, command, iterator, mediator, memento, observer, state, strategy, template method, visitor.

Python, Java, JavaScript, and C++. Design patterns are language independent as ideas, but they look quite different in practice depending on whether a language has interfaces, first class functions, or duck typing, so seeing more than one implementation is genuinely useful rather than redundant.

It helps, and the two fit together neatly. SOLID gives you the principles that explain why most of these patterns exist, so learning them first makes the patterns feel like consequences rather than a list to memorise. That said, this course does not assume it, and plenty of people arrive at the principles by way of the patterns instead.

The names are, even where the implementations have changed. Modern languages have absorbed some patterns into their syntax, and a few are used less than they were, but the vocabulary is still how engineers discuss design with each other. Saying "this is a strategy" in a review communicates a whole shape in three words, and being unable to follow that conversation is a real handicap.

Yes, in the low level design, object oriented design, and machine coding rounds. Naming a pattern scores you very little on its own. Explaining why you chose it over a neighbouring one, and what it costs, is what actually scores, which is why the pros and cons section of each lesson matters more than the class diagram.

31 lessons, essentially one per pattern plus an introduction and a summary for each family. Because the lessons are independent of one another, it also works as a reference you dip into when a specific pattern comes up, rather than something you must read front to back.

Text-based, with structure diagrams for every pattern and code alongside. Since you will mostly be comparing a diagram against an implementation, and later comparing one pattern against another, having them on a page beats watching them go past.

Yes. Design Gurus issues a certificate once you have completed the course, and you can share the link directly or add it to your LinkedIn profile.