You should refuse to develop what you don’t understand
Understanding is key to building quality software. Here are 3 levels of understanding we should go through before we start coding.
Recent Posts
A serious game for learning ‘built-in quality at the source’
Skip studying queuing theory! Play this 1h15 serious game for learning why building-in quality at the source leads to a productive and sustainable pace.
How to max out DDD Big Picture Event Storming with other Workshops
DDD Big Picture Event Storming is a prelude and catalyst to other workshops. Ex: Design Level Event Storming, Example Mapping, Story Mapping & Impact Map...
Feature Teams vs Component Teams? Decide with Event Storming and DDD
Team organization is tough. Event Storming builds enough shared knowledge and architecture for successful team re-organization workshops.
Rewrite vs Refactor? Get Insights from Event Storming and DDD
With legacy code, rewrite vs refactor is a valuable but tricky question. Here is an Event Storming activity that shows how far we are from the target.
Using Event Storming and DDD to prototype (micro)services and NFRs - 2
With Event Storming and DDD, we can draft services boundaries and NFR prototypes. In this post sequel, we’ll see that microservices are no silver bullet.
Using Event Storming and DDD to prototype (micro)services and NFRs - 1
DDD Big Picture Event Storming is a great support to draft (micro)services boundaries and NFR prototypes. Let’s see how to with this workshop activity.
How to use Event Storming and DDD for Evolutionary Architecture
Big Picture Event Storming and DDD let us share an architecture vision. Here is a way to realize it through evolutionary architecture and emergent design.