💡 Stories are an early part of the evolution of a feature. We use stories as temporary placeholders for communicating, estimating, and planning features (both functional and non-functional).
In the last chapter, we learned how to use Event Storming or Event Modelling to create a shared mental model of the domain.
At the end of either of these discovery-like workshops, we will have identified the vast majority of the business events, commands, and queries involved with creating the system we've been tasked to build. This puts us in an incredibly good place for the next steps: estimating and planning the features. How so? Because the commands and queries are the functional requirements…
This book’s mission is to teach developers the essential skills and practices to write testable, flexible, and maintainable code.
You can read more about the learning journey in the "Software Design and Architecture Roadmap 🖼️".
Already bought it?
If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.
You can read the intro to the book for free and visit solidbook.io to buy the book/wiki (it's currently on pre-sale for 33% off)! For recent updates, click here. To get an idea of my writing, read some of my best free content here and here.