In line with several other comments: 1) Programming is not the "the literacy of the 21st century." Come on. It isn't now and it never will be, unless languag

In line with several other comments: 1) Programming is not the "the literacy of the 21st century." Come on. It isn't now and it never will be, unless languages evolve to be essentially AIs that you can just request features in English, and even then it won't be, since most people won't bother to make programs. I'll go to the mat on this one. Those who bandy this idea around are misrepresenting reality. 2) Dan Miller, a career guru/author, has a point in one of his books that you should not attempt to strengthen your weaknesses--because then you end up with "strong weaknesses". Instead, strengthen your strengths. If you are good at soft skills, selling, design, idea man stuff, DO THAT, and leave the Model View Controller stuff to those who live and breathe that. You'll (likely) never do it as well as they do, anyway. 3) If you insist on learning to programming despite these two admonitions not to, I agree with many here who wrote: pick a project, and do it. And not some dopey toy project that you don't care about. Something real. I had an idea for an application years ago and have been working on it in my spare time and now feel that I can program, at least to some level. If you are in a company, work with the tech people to contribute to one module or one class or one feature, and start there. Become master of that section, and then move on.