this post was submitted on 09 Oct 2025
50 points (100.0% liked)

Programming

23074 readers
203 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
50
Which software design principles do you rely on most? (lemmy.dbzer0.com)
submitted 4 days ago by Davy_Jones@lemmy.dbzer0.com to c/programming@programming.dev
33 comments fedilink hide all child comments
 

I’m curious which software design principles you find most valuable in real projects.

Two concise summaries I’ve found:

you are viewing a single comment's thread
view the rest of the comments
[–] Garbagio@lemmy.zip 3 points 3 days ago (1 children)

Would you be willing to give an example of the second? I feel like my boss would throw a shitfit if I told him I wrote anything that even remotely alter prod

[–] ambitiousslab@lemmy.ml 2 points 2 days ago

Certainly! The line we don't cross is that we don't directly edit data. Every record in our database must be generated by the system itself. But, we can re-trigger behaviour, or select different flows, or tweak properties around the edges as much as we want.

For example:

  • Reflows - for every message that enters or leaves our system, we store it in a table. We can then reflow the message either into our system or to our downstreams. This means if there was a transient error or a code change since we received the message, we can replay it again without having to involve anyone else.
  • Triggers - i.e. ask the system to regenerate its output based on its inputs again. This is useful if there's a bug that's only hit in certain situations.
  • Migration - we have lots of different flows and some are triggered only on some accounts. We have some scripts that lets us turn on/off migration and then automatically reflow all the different messages.