R. Joseph Newton wrote: > I'm fatalistic. People rarely actually take my advice. I'm going to give > you some anyway. Suspend this project, and work on the process of > organizing your task into named subroutines. You have better things to do > with your mental powers than trying to keep track of how one line of code > is going to interact with hundreds or thousands of others. This might > delay your project somewhat, but in the long run, it will speed your work > dramatically. > > Break your problem down into manageable chunks.
I'm not fatalistic, and second this advice wholeheartedly. Breaking the problem down into smaller parts and when you are sure each separate part works properly, THEN working on interlacing and glueing them together, will make the overall issue MUCH clearer to you. It's also easier to figure out what each part is doing this way, if you need to make subtle changes at a later date... trust me on this. :o) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
