I've only been programming for 2.5 years, and never taken a single course in programming. I'm self taught.
It's just whatever I do, I put effort into learning. I don't program for a living, but could if I wanted to. In fact, I'm saving for college over the next 2 years so I can get a degree and be a meterologist/computer scientist.
But, as you said Xeon - you don't have to worry about that stuff in VB, you do in C++. But I don't worry about it, because 99% of the time, any bug I have produced has been a simple typo. (and == instead of an =, etc...) I just simply feel that limiting capability - and trying to 'protect' a programmer from mistakes, instead of trying to teach them how to be a better programmer, is the wrong course of action. Stick with the VB's, C#'s, and all the 'protective' languages and you'll be stuck there. I just feel it's people like me that work with C/C++/Assembly that will be the future OS writers/etc... And that is why I say Microsoft will fall to Linux eventually. (Not because of open source, but because of the way they are grooming their future clients) - Fact of the matter is, people don't like upgrading hardware. And MS has already written much of the .NET OS in C#, which runs at 60% the speed of C++. If this continues, a Windows OS will need a much faster CPU (and more RAM) to compete with other OS'es. Plus cover ups in bugs seems to always be another layer added on top to hide the bug, instead of fixing it directly. It multiplies by trying to create a user base highly dependent on the protective languages. Plus, we've already seen that the internet age will never replace the importance of the desktop (although for years people said it would. Even that Java would be the killer of C++ because of it, but we all see and know Java is not the be all or end all - and it's not as big as it once was - just look around the net) But, since this is going off topic, I'll leave it right there.
