Hacker News with Generative AI: Design Patterns

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

3 points by luu 2 days ago | 0 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 19 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 29 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 57 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 68 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 73 days ago | 62 comments

Dysfunctional Options Pattern in Go (rednafi.com)

Go, Programming, Software Design, Design Patterns

19 points by ingve 124 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 124 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 126 days ago | 14 comments

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