3 ms·
"The design is the code" does not follow from the idea that design and construction are not separate things in software. The thing to take away from that idea
by underdeserver 6y ago
"The design is the code" does not follow from the idea that design and construction are not separate things in software.
The thing to take away from that idea is that the design doc is not law written in stone, but a base for changes. It keeps your design honest on the high level. If you end up clashing with reality, and your design doesn't work out, you can backtrack to the design doc and refine it as necessary.
In short, the design doc should be a living document.
- nickbauman 6y agoI think what you're talking about here is an "intention document" not a design document. Design is about planning. Which implies you define things in detail with steps and techniques. Intentions are about what you want to achieve. Very different.
- maps7 6y agoA design is an outline, sketch, or plan. So it doesn't specify the level of detail.
- underdeserver 6y agoThe design doc is definitely the plan. But if the plan doesn't work when faced with reality, you need to change the plan, and therefore also the design doc.