Hacker News with Generative AI: Design Patterns

Standard patterns in choice-based games (2015) (wordpress.com)
When I was analysing the structures of CYOA works a few years back, I began to recognise some strong recurring design patterns.

Game Design, Choice-Based Games, Design Patterns

253 points by Ariarule 5 days ago | 69 comments

How to Write Complex Software (grantslatton.com)
Suppose you are implementing some complex piece of software — a database, a word processor, a filesystem, a web browser, whatever. How do you get started? How do you actually organize the code?

Software Development, Programming, Design Patterns

7 points by typingcyclist 15 days ago | 0 comments

Systems ideas that sound good but almost never work (learningbyshipping.com)
Some engineering patterns that sound good but almost never work as intended

Software Engineering, Design Patterns, Best Practices

419 points by kaycebasques 18 days ago | 261 comments

Enum of Arrays (tigerbeetle.com)
A popular data-oriented design pattern is a Struct of Arrays. Is an Array of Enums also useful? Yes! But let’s do a refresher on struct of arrays (SoA) first:

Data Structures, Programming, Design Patterns

145 points by signa11 28 days ago | 49 comments

Enum of Arrays (tigerbeetle.com)
A popular data-oriented design pattern is a Struct of Arrays. Is an Array of Enums also useful? Yes! But let’s do a refresher on struct of arrays (SoA) first:

Data Structures, Programming, Design Patterns

10 points by todsacerdoti 29 days ago | 0 comments

Visitor Pattern Considered Pointless – Use Pattern Switches Instead (nipafx.dev)
In modern Java, the visitor pattern is no longer needed. Using sealed types and switches with pattern matching achieves the same goals with less code and less complexity.

Java, Programming, Software Design, Design Patterns

3 points by signa11 29 days ago | 0 comments

Functional Core, Imperative Shell – Scott Wlaschin (youtube.com)

Functional Programming, Software Development, Programming Paradigms, Design Patterns

3 points by fuzztester 45 days ago | 1 comments

Thinking in Actors – Challenging your software modelling to be simpler (jeremycarterau.substack.com)
Challenging your software modelling techniques to be simpler

Software Development, Software Architecture, Design Patterns, Programming

135 points by jeremycarter 47 days ago | 45 comments

A C++ Mixin System (jennyjams.net)
I've had this idea in the back of my head for a while of pervasively using mixins to add code and logic for more high level concepts, although this gets somewhat close to Rust style traits (and C++ concepts). This has existed in the back of my head for a long time as a way to model a framework or standard library implementaiton while also providing it for user types.

C++, Object-Oriented Programming, Design Patterns, Software Design

74 points by luu 60 days ago | 40 comments

Traits are a local maximum (thunderseethe.dev)
Traits are one of the few programming language concepts beloved enough to earn multiple names.

Programming Languages, Design Patterns

121 points by emschwartz 60 days ago | 101 comments

Killing the Command message: should we use Events or Documents? (2007) (microsoft.com)
If we want to decouple a SOA system, we must get away from the notion of the remote procedure call. In other words, our services need to have as few "command" messages as we can get away with. This is a design philosophy but it is easier said than done.

SOA, Software Architecture, Design Patterns, Microservices

9 points by chipdart 77 days ago | 1 comments

State-shift: Macros for implementing Type-State-Pattern on your structs and met (github.com/ozgunozerk)

Programming, Software, Design Patterns, Macros, C#

13 points by todsacerdoti 86 days ago | 1 comments

Go and my realization about what I'll call the 'Promises' pattern (utoronto.ca)
Over on the Fediverse, I had a belated realization:

Go Programming, Design Patterns, Software Development

88 points by ingve 115 days ago | 95 comments

"Design It Twice"? (16elt.com)
Designing software is tough. I think we can all agree on that. No matter how much experience you have, your first idea about how to structure a module or system is usually not the best one. I had to learn this lesson the hard way, and I really wish I knew about the “design it twice” concept earlier in my career.

Software Development, Design Patterns, Programming

23 points by cookie-chan 126 days ago | 7 comments

Design Patterns Are Temporary, Language Features Are Forever (ptrtojoel.dev)
Design patterns are these cool things that make you go 'hell yeah' because they make a certain problem easier to deal with. Whether it's applicable to all languages, or due to a language constraint, they're pretty nice. Of course, some people go crazy with them rather than doing the simple thing that works. Other times, you'll naturally do a design pattern without even knowing about it.

Software Development, Programming Languages, Design Patterns

110 points by delifue 131 days ago | 62 comments

Dysfunctional Options Pattern in Go (rednafi.com)

Go, Programming, Software Design, Design Patterns

19 points by ingve 182 days ago | 8 comments

Why package by feature first and then by layer? (garrettdbates.com)

Software Development, Software Architecture, Design Patterns

4 points by garrettdbates 182 days ago | 1 comments

What to do if you don't want a default constructor? (sandordargo.com)

Programming, Object-Oriented Programming, Software Development, Design Patterns

57 points by jandeboevrie 184 days ago | 14 comments

C++ Design Patterns for Low-Latency Applications (hackaday.com)