51

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
[-] bleistift2@sopuli.xyz 6 points 6 days ago

Single responsibility. I deplore my backend developers who think that just because you’re mauling a single (Java) stream for an extended operation, it’s ok to write a single wall-of-text, 5 lines long, 160 characters wide. Use fucking line breaks, for fuck’s sake!

[-] phoenixz@lemmy.ca 2 points 6 days ago

On 4K monitors, 160 character lines can be quite nice, though you may not want a wall of that, yeah

[-] furrowsofar@beehaw.org 1 points 6 days ago

Common:

  • Procedural, preferably Functional. If you need a procedure or function use a proceedure or function.
  • Object Oriented. If you need an object use an object.
  • Modular
  • Package/Collection if Modules
  • Do not optimize unless you need to.
  • Readable is more important then compact.

Frankly everything else is specialized though not unuseful.

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

Programming

23108 readers
78 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