>Committing to dates and then being accountable for the results Being forced to commit to dates, as only a soothsayer would dare. >Spending time planning, rat

>Committing to dates and then being accountable for the results Being forced to commit to dates, as only a soothsayer would dare. >Spending time planning, rather than "doing" Because "doing", as you say, helps planning. Development is not production (which is compilation), it's conception all the way, it's the non-automatable and hard to estimate phase of creating order out of void and chaos, by completing up to a complexity that no one can hold at once in his mind, and precising unambiguously into a formal language, some vague expectations expressed in a natural language, or some creation imagined by the developer himself. Preventing a developer from "doing" is like preventing a mathematician from interacting with his board. Manufacturing: repetitive, predictable. Mindfacturing: non-repetitive, unpredictable. Related quotes: "Programming is a good medium for expressing poorly understood and sloppily-formulated ideas." (Marvin Minsky) "The computer revolution is a revolution in the way we think and the way we express what we think." "My real goal is to transform things that are hard to understand into things that are easy to understand, and programming has been one of the tools in doing that." "I always learn things by writing programs." "Clarity sometimes need programming because (...) if I write a program that doesn't represent something sensible, I get an error." (G. J. Sussman, https://www.infoq.com/presentations/Expression-of-Ideas https://www.infoq.com/presentations/Expression-of-Ideas) "What I cannot create, I do not understand." (R. Feynmann) "A number of people are desperately waiting for the software industry to reach some kind of maturity and start resembling traditional industries. They will have to wait forever." (V. Lextrait, Mindfacturing)