Design patterns are among those topics that are often dismissed as "outdated." It’s true that the explicit patterns in the Gang-of-Four book apply only to OO & could use an overhauling. (Command, for example, needs to be reexamined in the light of Lambdas.) BUT… 1/4
The important thing is learning to think in patterns, not to memorize specific ones. When you look at systems designed independently by different people, focusing on specific problems or issues and how they’re addressed, patterns emerge. 2/4
Some solutions seem to pop up spontaneously in many places. There are infinite variations in the details, but the core approaches are eerily similar. Those are design patterns. Keep an eye out for them and try to remember them when you see them. Given them a name. 3/4
The next time you find a similar problem or issue in your own code, you’re one step ahead in developing a solution that’s tailored to your specific context. You also now have a shared vocabulary with other architects. That’s invaluable. 4/4
• • •
Missing some Tweet in this thread? You can try to
force a refresh
