4 ms·
Interesting to see all of the discussion on hard-coding vs configuring domain/business logic, when in reality most line-of-business app developers are never int
by arwhatever 6y ago
Interesting to see all of the discussion on hard-coding vs configuring domain/business logic, when in reality most line-of-business app developers are never introduced to the very concept of business/domain logic, and therefore it gets strewn all throughout an application’s code based, tangled in with data retrieval, u/i concerns, and everything else.
- bopbeepboop 6y agoYes — the goal of DDD is to explain why that’s a bad idea. For two reasons. 1. It makes your code a mess. 2. You probably wrote the wrong thing anyway, because how do you know what the customer wants if you don’t even know what they do? DDD argues you should develop software by: 1. Talking to customers about the domain until you have a shared language with specific terminology. 2. Write that down as a model. 3. Write that model as software. I think one of the biggest misses in software engineering (and something I’ve seen cost $100Ms) is software developers not talking to customers about what they do with the software. Some of the worst bugs happen because domain experts mean something by a term of art that software developers misunderstand. DDD overlaps heavily with the “applied category theory” perspective on software, so DDD tends to be popular with functional programming types.
- kthejoker2 6y agoThis is literally why Fowler and Evans wrote their books, some of this "tangling" was viewed as a feature because it let a single dev own an issue and avoided the bottleneck of architecture by committee.