Reply to thread

Message: [QUOTE="James Kanze, post: 3484426"] I don't think you really mean it that way, but it sounds like you're suggesting making stabs in the dark. I think the important point is to understand what you are going to write before writing it. I've seen a lot of second rate programmers using the debugger to try to understand what they've just written. That's wrong, and never gives good results. But just writing random code, and then making random changes until it passes the test suite isn't any better. The only general rule that works is think first, then act. Don't write a single line of code without knowing why---what the purpose of that line is, what the state of the program is before the line is executed, and what it will be after, etc. [/QUOTE]