Jared Norman (@jardo.dev)

My take: software design patterns are good tools for describing designs and for making it easier for people to understand designs, but are not good tools for designing software. purplesyringa.moe/blog/if-i-h...

loading . . .

If I hear "design pattern" one more time, I'll go mad Here, read the intro of the Wikipedia page for Command pattern with me: In object-oriented programming, the command pattern is a behavioral design pattern in which an object is used to encapsulate all information needed to perform an action or trigger an event at a later time. You know what I call this? A function. This information includes the method name, the object that owns the method and values for the method parameters. Here’s your command: const command = () => object.method(arg1, arg2); // or in PHP, or in Rust, or in C++... Every time I hear about a design pattern I don’t recognize, I get afraid that I’m missing some crucial idea, and then I Google it and find out that I’ve been unknowingly using it since I started programming. Yeah, bro, I used the data store pattern earlier today (a variable). https://purplesyringa.moe/blog/if-i-hear-design-pattern-one-more-time-ill-go-mad/