this post was submitted on 13 May 2026
10 points (70.8% liked)
Programming
26915 readers
547 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
domain-driven design (or development?)
I'm not 100% what it is (I'm really not into nomenclature), but I think it's the practice of modeling your software after the domain you are working in... IDK if/how it differs from what everyone has always been doing since forever.
My understanding is there was a group that was saying to combine stuff by use. So you have a class to determine total price, but you sell liquids priced by liter, gasses sold by cubic foot, and solids sold by quantity. Each of those are controlled by separate departments and require different methods of calculating price.
DDD basically says to group everything for liquids together, everything for gasses together and same for solids. Don't group by process but by who uses them.
In theory, yes. In practice, not what happens. Throughout my experience I've seen business logic scattered everywhere.