Don’t Use Design Patterns, but Know Them — Master Them!
Behind this catchy title (sorry) lies one of my dearest pieces of advice, nurtured by ...
For further actions, you may consider blocking this person and/or reporting abuse
Well said. The most important use I've found for design patterns isn't implementing them, but when trying to describe a part of the codebase/architecture: "it's a bit like a state machine, where those sections there function something along the lines of a strategy pattern, where the input here mostly comes from observer-like loose dependencies" (or something less convoluted :) ).