Somewhat tangential thought here. I learned to program way back in the stone age (think punch cards, job control, and Fortran). So that's probably not immediately relevant. What is relevant (besides having a problem to solve) is being aware that if you're thinking of programming as a vocation, you're committing to a LOT of learning. Programming evolves; we know how to do things a lot better than we used to; we have better infrastructure and hardware than we used to; we're able to design languages with better internal constructs. So think of languages as tools in the toolkit that can be applied when appropriate, and the tools change over time. In my life as a programmer(), I've learned Fortran, Job Control, Assembler (various), Pl/1, Pascal, Basic, Visual Basic, C, C+, Java, Ruby, Groovy, php, python, javascript, html, blah, blah, etc, etc, currently starting to look at functional programming languages. My point being there's always something new (and interesting) to learn, and it's part of the job.

tl;dr - Learning programming never stops