When to go from collaborative modelling to coding?
summary
Answer: treat “when to stop modeling and start coding” as a polarity not a problem: map the two poles (collaborative modelling and coding) with upsides/downsides, name Barry Johnson Polarity Mapping on a whiteboard, list concrete signals (many code comments, hacky fixes, people checking phones, no stakeholder feedback) and matching actions or heuristics (implement the 80% path, code an MVP from the model, model the hacks). The map yields specific observable triggers and one-to-one or many-to-one remedies, preventing crusading or self‑fulfilling failures.
AI-written summary · about
chapters (20)
- 0:00Intro
- 5:41Why should we care
- 11:10Visualising the polarity
- 15:31Fun fact
- 19:11Live action
- 26:56Disney knowledge
- 29:56Signals and observations
- 35:31Managing polarity
- 36:36How to spot polarity
- 40:31Examples of polarity
- 42:01completeness vs accuracy
- 45:36crusading
- 46:21toilet paper example
- 48:01finding balance
- 49:36the last fun fact
- 50:31why does coding go wrong
- 50:56how long would you do this
- 52:16the problem
- 52:51the problem in coding
- 53:56outro
related talks
29mModeling on the Right Side of the Brain
48mTechnical Modeling as a Practice
48mGrowing & Thriving in a Multi-model World
43mGood Fences Make Good Neighbours
39mModel Drift and Software Attractors
51mUXDD: A New Pragmatic Methodology for Domain Modeling and User Experience.
25mHow to use Example Mapping and 3 amigo sessions to shift left
33mRefactoring with Observability