The right way to think about "Design Patterns" in programming is that they are a helpful descriptor. It's easier to say "I'm using a builder here" than describe the details that go into the builder pattern.
And that's it.
Design Patterns are not a goal in itself, they don't make code better, neither they are bad. They are just a name assigned to something that is so commonly done that it got a name to make the conversation faster.
dpc
npub1ya…t0gd0
2023-02-28 00:11:55
Author Public Key
npub1yarprdrj3vxyp0su7xqd3u6z047na6792ezas6dqqt5tv4lce4ssjt0gd0Published at
2023-02-28 00:11:55Event JSON
{
"id": "34005426530f05d90eded83a05d92d7e7f1514c4596ed06a490e129cf44500c6",
"pubkey": "274611b4728b0c40be1cf180d8f3427d7d3eebc55645d869a002e8b657f8cd61",
"created_at": 1677539515,
"kind": 1,
"tags": [],
"content": "The right way to think about \"Design Patterns\" in programming is that they are a helpful descriptor. It's easier to say \"I'm using a builder here\" than describe the details that go into the builder pattern.\n\nAnd that's it.\n\nDesign Patterns are not a goal in itself, they don't make code better, neither they are bad. They are just a name assigned to something that is so commonly done that it got a name to make the conversation faster.",
"sig": "86a3b9f86ed8a4aacfaaeff4063ecf8ca15932bbfee481aacb50509fce02887aa5abb2a7f6366824994bab6c949a605efd75f558f3dc1dc5dddb4cfa95c91ff1"
}