I like to program in tiny little baby steps. I write one line of code and then check to see if it compiles. (I use a fancy IDE that checks syntax continuously as I type.) This way, whenever I do have a compiler error, I have a pretty good idea of exactly where it is, and it's usually pretty easy to recognize the mistake quickly.
I've run into quite a few very new programmers that had the habit of writing dozens of lines of code before seeing what the compiler had to say about what things. These folks also seemed to have problems figuring out fixing the dizzying web of errors they'd often face. [ September 11, 2004: Message edited by: Dirk Schreckmann ]