HN Explorer

6 comments

[ 3.5 ms ] story [ 25.1 ms ] thread
Quokka-labs
The biggest shift is treating tests and constraints as the source of truth, not the generated code.
m110
Isn't code what defines the constraints though?
rrook
The domain and delivery/ops context define the constraints, code that gets written ought reflect those constraints, not provide more.
rrook
Sure, the domain model isn't an artifact, but software _necessarily_ contains an artifact of the domain model.
m110
Makes sense, but this artifact is still a simplification, right? The domain model isn't just this one artifact in the code but the broader "idea".
rrook
Absolutely - it's like, the "current agreed upon version", but indeed it's a point-in-time snapshot/simplification of whatever the thing being modeled actually is.