Elektrine lite

← Feed

@fabs@mastodon.gamedev.place

Post #778250

2024-02-29 07:31 UTC

Ever wondered why Design Patterns didn't take off? Did you ever wonder how they became so all-pervasive but also so empty and soulless? Those were the sparking thoughts behind this book. It's taken four years of research and way too much of my spare time. Go check out Unresolved Forces: https://www.unresolvedforces.com/ #amwriting #ampublishing

Replies (10)

  • @fabs@mastodon.gamedev.place It is interesting how much of the book's bibliography I have heard of, own(ed), read, reviewed before publication, or written for. :-)

    Open ##2437899

  • @gregdavis@hachyderm.io 2024-03-01 13:29

    @fabs@mastodon.gamedev.place I really love the line, "like claiming you know how to cook when your culinary expertise only stretches to five different ways to make eggs on toast."

    Open ##2437901

  • @ekuber@hachyderm.io 2024-03-01 19:07

    @fabs@mastodon.gamedev.place one thing I've noticed is that actually useful and common patterns eventually "disappear" because their functionality becomes one or more language features that end up being much easier to deal with.

    Open ##2437902

  • @aredridel@kolektiva.social 2024-03-04 02:49

    @fabs@mastodon.gamedev.place @ceejbot@toot.cat Oh this is wonderful, thank you!

    Open ##2437906

  • @nf3xn@mastodon.social 2024-03-04 03:50

    @fabs@mastodon.gamedev.place I'm not sure it "didn't take off" is quite accurate. Certainly had to put up with it enough. I do remember though that most of these fads are a rehash of what went before like the MVC/MVT nonsense wasn't just a misunderstanding of a three-tier schema architecture. Then there were a lot of people like McConnell who had no clue and yet every techbro seemed to think they had it solved just because they worked at Microsoft forgeting what the Longbeards had taught only to have to reinvent it.

    Open ##2437908

  • @villares@ciberlandia.pt 2024-03-04 10:50

    @fabs@mastodon.gamedev.place I wonder why don't people acknowledge the original inventor of Design Patterns, in the domain of architecture, Christopher Alexander.

    Open ##2437909

  • @drj@typo.social 2024-03-04 11:55

    @fabs@mastodon.gamedev.place because even at the time they were written, many languages could and had incorporated the design patterns into the language. They didn't need an external dogma.

    Open ##2437911

  • @fabs@mastodon.gamedev.place Interesting. I'm pretty sure Design Patterns were embedded in things like frameworks and libraries for OO languages such as Java. I remember trying to figure out how to use GoF patterns when learning Java many years ago. When I started learning functional programming (Scala) later, I discovered you don't need half the GoF patterns in FP, because they're basically about tricking an object into adding new behaviour. In FP you can just pass behaviour around via functions. Much easier!

    Open ##2437913

  • @ve7fim@mastodon.social 2024-03-05 02:53

    @fabs@mastodon.gamedev.place One anti-pattern that likely influenced the shift in how design patterns have been understood over the last 30 years is "that which is easy to test (especially with multiple choice questions) is what tends to get taught". :(

    Open ##2437915

  • @fabs@mastodon.gamedev.place Just found out about this book from you post elsewhere, it took me a while to notice that you are also the author. It is so intriguing I actually paused a Stephen King book for this. I learned to be wary of anyone claiming they know what they're talking about in software design, but this is on a pretty good start.

    Open ##2437916