9
You might not need… the always-valid entity
(www.jayfreestone.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2026
9 points (80.0% liked)
Programming
27651 readers
118 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 3 years ago
MODERATORS
TL;DR:
Domain Driven Design has a flaw: not all types can be categorized into "valid" and "invalid", since it often depends on context.
Solution: you just haven't modeled your domain correctly. You have a type for "MyData" but you don't have a type for "MyDataThatIsBeingEditedByTheUser".
So the "final" type should be valid, but often you should have intermediate type(s) that model incomplete input.
Basically, when doing DDD don't forget your builder types.