-=> Quoting David Chord to All <=-
 DC> Just wondering how normal or abnormal I am.
 DC> When I implement a feature or part of it, I compile the program to see
 DC> if that part of it is actually going to run, and if it doesn't run as
 DC> expected I do further testing or learning on it. This can be every few
 DC> minutes of course, and can take some time, but I believe it helps
 DC> ensure that the beta release is quite close to bug-free.
 DC> Does anyone else program like this? Does any one else have any
 DC> suggestions? 
 DC> Bye..
Hehe, I program like that all the time.  I make SURE that a more
complicated part of the program is going to run before adding anything
else.  That way if you start having problems, you'll know exactly what part
is causing it.  I've heard of some people that just constantly code, not even
compiling to see if they made any typos or syntax errors by mistake.  I
won't put down this method of programming, but that's sure a good way to do
it if you want to spend the next day smashing the keyboard over your head
when you can't find where a problem is.  :)  But of course, the most
important thing to remember is that everyone programs differently.  There
is no "normal" or "abnormal" way to do it.  So if somebody thinks you
program in a weird way, that probably means they program even weirder.  :)
... Ithinkmyspacebarstoppedworking.
___ Blue Wave/DOS v2.30
--- Platinum Xpress/Win/Wildcat5! v2.0
---------------