I don't know if you remember the early MS Office spellcheck that didn't highlight misspelled words. It just had the ability to run a program and it would check your errors. Did you ever use it?
How often did you run it? Every line? I know that I would only run it when I was finished, and that's no matter how many errors I knew I would have. It's a time on task matter. I keep my mind on writing the code, then I go back and fix errors. If I make an update to code, I make the update, then I compile to see if it all went well.
To me it doesn't matter how new you are, you should never be doing code that generates more errors than you can handle. If you can't get through a "Hello World" program with little error then perhaps you shouldn't go further than that until you can. This is my whole point. People do something, and make mistakes, they do it again, and make less mistakes but still a decent amount. An amount that they just brush off as small mistakes and then they move on. They continue the same method piling on mistakes until they reach a program and get overwhelmed. I don't like seeing people in this situation and it doesn't have to happen this way.
Please don't compare what I'm saying to anything but a learning programmer compiling a lot. I'm not talking about updating and maintaining a project that's in use and needs to be coded perfect at all updates. If you want to tell me you should compile all the time with that, then I say fine. You're right. This is different though, I'm talking about a learning process, not an efficiency or precision thing.