News for hackers. Stuff that matters.
Re:Why Domain Driven Design? by still_grokking on Friday November 25, 2022 @05:53AM (#33741187)
This sounds brilliant!

What's the marketing name for that?

Re:Why Domain Driven Design? by withinboredom on Friday November 25, 2022 @06:16AM (#33741326)
I’ve called it Model-T development[1]. The Model-T brought standardization to building cars where companies only built to a very specific spec. It didn’t matter that some companies would be better than others, or cheaper/expensive. The point was choice, competition, and interchangeable parts. Granted, I don’t actually know about that, but that’s the end result.

[1]: I apparently deleted the post so I’ll have to undelete it and come update this comment.

Re:Why Domain Driven Design? by goto11 on Friday November 25, 2022 @06:10AM (#33741289)
"Lose coupling"
Re:Why Domain Driven Design? by layer8 on Friday November 25, 2022 @09:08AM (#33742495)
It’s called separating interface from implementation. When using an interface, only make assumptions on what the interface specifies, and not on how it may happen to be implemented. When implementing an interface, only make assumptions on what the interface specifies, and not on how it may happen to be used.
Re:Why Domain Driven Design? by gadflyinyoureye on Friday November 25, 2022 @02:05PM (#33745707)
Even this confuses people. Often the name of the interface is something like S3Client. No, the name should be something like PolicyWriter.
Re:Why Domain Driven Design? by cutemonster on Friday November 25, 2022 @07:07PM (#33748377)
It's called Microcompanies.

>> Otherwise [without microcompanies] you just can't do software engineering right.

So true