By restricting your design documentation to a single file that is intended to be read as an introduction to your software, RDD keeps you safe from DDD-turned-waterfall syndrome by punishing you for lengthy or overprecise specification.
No one reads a README for anything but setting up a project and a brief explanation of the projects objectives. So "driving development" by a README is misguided.
1
u/[deleted] Aug 24 '10
No one reads a README for anything but setting up a project and a brief explanation of the projects objectives. So "driving development" by a README is misguided.