3 ms·

I don't believe that to be true, and I have never met a developer who thought that to be true. Sketches and diagrams can design a large system, but at the end o

• edejong 12y ago
  The best and lowest-maintenance pieces of code our team has written were carefully designed and thought out before a line of code was written. I'd say 20% of the actual work was coding, 30%/30% for design and testing and 10%/10% for requirements analysis and deployment. However, often we know that we don't know how to properly design something and we start implementing too early. The end result is sth like: 50% coding, 30% testing and the rest is squeezed into testing, deployment and requirements analysis.
  • bsaul 12y ago
    Starting on a paper instead of coding directly is really the key to the best quality software i've done. Funilly i realized that very early at university, where i had to perform a code exercice while on holidays, but forgot to take my computer with my me. I did it on paper, then typed it when coming back home, and got the best grade.