3 ms·
This is why Domain Driven Design should be mandatory reading for all anyone making decisions on Software Architecture.
by radicalbyte 6y ago
This is why Domain Driven Design should be mandatory reading for all anyone making decisions on Software Architecture.
- datavirtue 6y agoAgreed. But do we mandate that they understand it and somehow enforce their implementation competency? As pervasive and helpful and as easy to understand what Clean Code is, it is still very rare to find someone who understands it and applies it in the field.
- hackerfromthefu 6y agoUnfortunately in actual practise I've encountered significant cargo culting about DDD. Attracts a lot of people with mid level experience who suddenly want to dictate architecture based on theoretical ideals rather than practicalities. There's no substitute for experience, and specifics of adapting architecture to the context of the problem you're trying to solve. In one case I wanted to use a technology that actually matches DDD very significantly - but the cargo cultish closedmindedness of the practitioners meant they couldn't even understand how an old idea/tech they hadn't liked or approved was, was actually an implementation of DDD. The problem there is not DDD, the problem is the people who get closed minded and stuck to their one true way (often without really broad experience to make that judgement call effectively). I've learned that pattern of language of absolutes such as 'should be, mandatory, all' do XXX is often a sign of that kind of cargo cultish thinking.
- radicalbyte 6y agoThat's very true, and a problem I've also seen. There are an army of mediocre people who've gone full Cargo Cult with it. Usually comes with a big dose of Uncle Bob: The Bad Parts.