3 ms·
In my experience, no design document, no matter how carefully drafted survives contact with the enemy^W^W an IDE. At best you can define interface boundaries be
by gpderetta 11y ago
In my experience, no design document, no matter how carefully drafted survives contact with the enemy^W^W an IDE. At best you can define interface boundaries between independently developed modules.
Edit: broken leftover line
- fishnchips 11y agoThings change a lot during the project, I agree. But assuming everything will change and using that as an excuse not to plan at all sounds like a poor choice to me. "In preparing for battle I have always found that plans are useless, but planning is indispensable." - Dwight D. Eisenhower
- gpderetta 11y agoI do actually agree that some amount of planning, and especially putting down a sketch on paper do help, in particular as a way to nail down requirements and figuring out obvious roadstops, but it is important to be under no illusion that the final project will resemble in any way the plan
- lmm 11y ago> But assuming everything will change and using that as an excuse not to plan at all sounds like a poor choice to me. I know that's how it sounds. But in my experience it turns out to be a lot more effective than planning.