The tool can help reduce errors, at least syntax type errors. I can't count how many bugs I got in my applications because a variable was mispelled. The chance of this occuring in a strongly-typed tool is much reduced. To protect my applications for this kind of errors in VFP force me to do a much more extensive coverage test, which is very time-consuming.

Catching these errors at compile time (or even in typing mode) is far less expensive in development time than finding them at test or, worst of all, at production time.


I'm a fan of IntelliSense and strong-typing and discovery, but to be honest, that's what testing is for. Those who argue about writing test scripts early-on (an argument that I won't debate against) would say that's part of a developer's job.

Again, the tool can help with the development process, but Woody was talking about delivering an app that was closer to error-free. To me, when you get to that stage, it's far more about the developer.

(Jim N., no need to send me candy and flowers) :)