Event Storming is fundamentally changing the approach to strategic patterns and software development in general. I can't understand why this technique isn't used by every team in the world yet. Event Storming is a workshop where people who have questions (usually developers) meet people who have answers (usually stakeholders). During the session, they can quickly deal with complex business domains together. At the beginning, you research domain events (glue orange stickers). Event Storming is so flexible that you can use it to check if your solution meets the expected requirements. You can also set a different goal for the session, such as exploring data flows, potential issues, or UX. It's also tempting to save time during the project planning phase so that you can start coding as soon as possible and finish early. My favorite phrase in this case is "five days of coding can save one day of planning." Unasked questions won't magically dissolve. The best way to overcome the Dark Ages of Development is to attack them from different angles. Let's see how DDD patterns can attack this system.
0 Comments
If anyone asks me if there is any silver bullet in product development, I have only one candidate: strategic patterns. Strategic DDD helps us find answers to the questions: what problem are you solving? will your solution meet stakeholder and user expectations? how complex is the project? what features are not necessary? how to separate services to support rapid development in the long run? These questions are necessary both when implementing a new project, and when adding new functionality or refactoring. The strategic patterns of DDD enable us to answer these questions in a holistic and predictable way. Some engineers tell me they are "just engineers". They don't care too much about who uses their software and why. They just do, say, tasks from JIRA: they create services with some bytes in and some bytes out. This way of thinking leads to a big gap between engineers and their clients, the problems that we, as engineers, are trying to solve. Without sufficient communication, it is not easy to create a solution that will help people in the right way. But the goal is precisely this, and not just processing bytes. |
AuthorCustom software development ArchivesCategories |