Live data from Hacker News

Domain Storytelling: A DDD tool to visualize domain stories in the browser

domainstorytelling.org

1–10 of 17 posts

Re: Domain Storytelling: A DDD tool to visualize domain stories in the browser

#7
What are the advantages/disadvantages you've found over event storming? Is this just a good way to knowledge crunch with stakeholders to get to a good analysis model, or do you find it leads to specific learnings you don't get with any other method?

Re: Domain Storytelling: A DDD tool to visualize domain stories in the browser

#9

Erm UML rediscovered? :]

Nope. UML is a language for describing software systems. It's software first. Domain-Driven Design is a focus on understanding the actual concepts of domain experts. So this is people first.

As Martin Fowler said, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” That's much more likely to happen if programmers start with the existing human understanding of the situation.

As a contrast, let me describe two terrible code bases I worked on. The first was something built by roving gangs of consultants. It was about donations and corporate matching, but that was hard to tell by the code. It was basically a giant snarl of HashMaps with magic keys that got passed around all over the place, with bits of code fishing out things they needed. It mostly worked, but it was incredibly hard to sort out because the code didn't mean anything.

Another is the typical Java enterprise mess. I was once called in to advise on an open-source product that was being built by consultants used to doing banking work. Between being fetched from the database and rendered on the screen, data was copied from object to object 7 different times. ThisBean and ThatBean and DTOFactoryIntializerStrategy. Most of the code base wasn't really about the domain, it was cargo-cult rituals and architectural patterns that had no practical value. Worse, having the domain knowledge smeared out over a zillion objects means that their early domain understanding was locked in, so the code base and the way people talked about the domain drifter further and further apart.

At this point I'm a firm believer in Domain-Driven Design. If you really understand how people think about what they do and then build the system in those terms, you'll get a much better code base and a much better user experience. Domain concepts are generally very stable, so your design is less likely to go obsolete.

A good example is yesterday's article about building a real-time editing system. They got good code because they really thought about the human experience and then built in those terms: https://news.ycombinator.com/item?id=18220020

Re: Domain Storytelling: A DDD tool to visualize domain stories in the browser

#10
post #9

Erm UML rediscovered? :]

Nope. UML is a language for describing software systems. It's software first. Domain-Driven Design is a focus on understanding the actual concepts of domain experts. So this is people first. As Martin Fowler said, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” That's much more likely to happen if programmers start with the existing human understanding…

There seems to be some overlap with a UML business use case which can be used for modelling requirements.
Post reply on HN