Coding is an underestimated part of the design. When we think about the design, we immediately fall to whiteboard diagrams, sticky notes, or endless discussions. That’s fine and one way of doing things, but we should do more - prototyping and working with code during the design phase. I mentioned last time that we don’t need to fall into Test-Driven Development or Behaviour-Driven Design immediately. I showed before my approach to composing business logic; today, I’d like to expand on that. We’ll use the following pieces in our recipe: Type-Driven Design, Decider pattern, Event Sourcing, and code that with C# and Marten. Type-Driven Design focuses on shaping our types in a way that doesn’t allow unexpected scenarios to happen. ... (The summary continues with the rest of the text)
