In my intro comp-sci classes years and years ago, my professor used to describe this as the difference between "hacking" and "software engineering". "Hacking" was the interative try/fail/fix cycle, driven more by intuition than by design. "Software engineering" was supposed to replace that by designing it right the first time so that debugging was errors in coding, not errors in design.
Ironically -- or maybe intentionally -- test-driven-development is just a structured (software engineering) approach to the "try/fail/fix" cycle:
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: brilliance or... easy erasure?
by xdg
in thread brilliance or... easy erasure?
by samizdat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |