Doodle-Driven Development
summary
Claim: drawing compact state diagrams yields clearer shared understanding than six Gherkin scenarios and speeds discovery. Team uses Graphviz/text diagrams (also tried Mermaid and SVG) sized around one or two rules so each box/arrow represents a business rule. A small PHP test runner parses the diagram source, applies events, asserts resulting state — intentionally brittle so failures surface early. Diagram images live in READMEs and feed exploratory event sequences to subject experts who quickly spot wrong behavior.
AI-written summary · about
chapters (7)
- 0:00Introduction to doodle-driven development
- 3:09BDD process and verbal communication
- 6:00Discovery with state machines and drawings
- 9:36Choosing the right drawing format
- 12:49Living documentation and automation
- 16:26Exploratory testing with diagrams
- 17:51Q&A on interpretations and brittleness
related talks
49mFrom Doodles to Dashboards, Data Flows, and Docs
45mA Picture is Worth 1000 Lines of Code
15mDraw me a software or the art of diagrams that stick in the mind
07mCan software developers draw pictures?
41mDesign Patterns for Software Diagramming
27mMaking Application Logic Visually Collaborative
27mDeeper Understanding & Better Communication through Art
05mLightning Talk: Doodling for Great Success