> So I was told this as bluntly as possible by someone 15 years ago - "you don't have to code all parts of your design". I would say that's more false then tru

> So I was told this as bluntly as possible by someone 15 years ago - "you don't have to code all parts of your design". I would say that's more false then true. Why? Because the design you haven't coded is a fantasy design. I'll give you a counter-quite, and excuse the military context: "No plan survives contact with the enemy" (simplification of a longer quote by Helmuth von Moltke.) I have yet to make any non-trivial design which does not require significant changes while it is being coded. Perhaps some design geniuses with much deeper insight can make this happen - but those are very few. Most people probably need several rounds of implementation and user interaction before reaching an acceptable design. So those parts of your design which you haven't coded are likely partially irrelevant and un-implementable. This is not to say that you should write huge amounts of code. But - try to avoid designing much beyond what you actually code.