
Originally Posted by
Amastacia
There's only one thing I haven't seen come up, which shocks me.
Learn to document what you do. Then learn to document it better. Then learn to document it even better than that.
Document what you're going to do.
Document what you're doing.
Document what you've done.
Document anything that you're doing in an unusual way.
Document anything else that you're thinking about seriously.
Document some more.
Beyond that, Aurik is on the money, along with several others.
Oh, and just to reinforce... before you start spending money on courses, use some of the information available on the web and free tools to just do some simple stuff. You'll get a feel fairly quickly if the style of problem solving and basic methodologies that good code development require appeal to you.
I, for one, loved the idea of computer programming right up until I went to school for it. I'm better off for what I learned, but the most valuable thing I took away besides a piece of paper is that the problem solving aspects appeal to me a lot more than the rote work. Thus, I'm now a sales engineer, because I get to keep solving problems, get to keep designing systems, get to keep my integrity, and don't have to sit in a box and code. I can still make little programs to solve problems for myself if I need to, but it's on my own terms and my own schedule.