
…greenfield or brownfield, when you’re dropped into a software project you are expected to deliver.
Rich visual information that clearly communicates important technical and non-technical information, such as key business differentiators, organisational constraints, and the proposed/existing technological configuration is essential for getting upto speed.
I use Domain-Driven Architecture Diagrams to satisfy this need and I encourage you to do the same.…
…. Sometimes you can create them on the whiteboard and throw them away once you’ve written the code. My heuristic is to maintain domain concept diagrams for the fundamental policies that are key to a business’s value propositions or concepts that cannot be fully expressed in code.
Every complex domain has intricate business rules, policies and workflows. Before you can model them in code, you need to work with domain experts to create strong neural pathways, giving you the confidence to implement.
In these scenarios, diagrams are useful. Aim to work with domain experts to create technical-jarg…