Domain Modeling Made Functional

What’s Next

Having spent the last four chapters doing nothing but modeling, we have reached the end at last and can finally start getting our hands dirty with a real implementation!

Let’s just clarify something before we move on. In this book, we’ve separated requirements gathering, modeling, and coding into distinct sections. This may look like we are encouraging a linear “waterfall” model of development, but this isn’t the intention at all. On a real project, we should be continually mixing requirements gathering with modeling and modeling with prototyping, whatever it takes to get feedback to the customer or domain expert as soon as possible. In fact, the whole point of modeling with types is so we can go from requirements to modeling and ...