in reply to Speedy Hacking
The worse the code you are cranking, the easier it is to crank it. Furthermore the higher the bug counts. But they are all simple bugs so they are easy to fix. Thus giving the illusion of a highly productive programmer.
However when you attempt to measure productivity by producing a measure of how long it takes to get the same task done, the most productive coders spend the least time actually typing code. Instead they spend time on activities like design, review, and so on that head off bugs before they start. When you consider that the majority of your time is spent in repairing code, when you just race ahead it is like paying in credit. You will have to pay back with interest before you are done.
If you want to understand more about productivity, I strongly recommend Rapid Development : Taming Wild Software Schedules by Steve McConnell. (Glancing through the reviews I am surprised that there are as many 4's as there are. Oh well) Of course at your stage you might benefit more from Code Complete by the same author.
Now you have indicated in the past that you think I am just a Linux troll. So let me point out up front that those two books I just recommended for you are published by Microsoft Press by an author who works as a consultant for, among other companies, Microsoft. They also have some of the best advice that I have ever seen on how to program well. I don't believe in turning down good advice just because I dislike the source. I strongly recommend that you not turn down this advice either.