(* The design and analysis phase are usually both longer then the time spent in the physical typing and programming portion of the program. When you add in testing, debugging, documentation, and so on, you find that for complex problems the coding phase is often less then 25% of the overall project time. *)

IIRC, Paul Graham suggested that he sort of "hacked his way into" his zillion-dollar application. IOW, an organic kind of growth rather than up-front planning. Also, he would probably say, "less code == less to debug". He also said something like, "There is less things to slow you down when you toss the suits out". [paraphrased]

I would definitely agree with the suits claim. Well, maybe not toss them, but simply give them an information-finding role only. They have a habbit of sticking their fingers into the pie simply because they want their fingers in there.