Hrm. If you want to learn "programming" the first step is to learn how a computer works, and how to translate the problem you're trying to solve into a form that is suitable for solution by a computer.
A mistake I see people make is that they learn a programming language, rather than learning how to program. If you learn how to program, it doesn't matter what language you use; the language just becomes a tool, and you learn which language is most suitable for a particular task. If you don't understand how to think about problems "like a computer" then just focusing on, say, C# instead of Lisp is going to do you no good.
While people are indeed working to come up with "natural language computing," we're not there yet. In fact, this is kind of a fruitless task in my mind: think about when you give instructions to another human and how they have trouble doing exactly what you thought you told them and instead do something else (that is, "natural language" is actually a pretty poor language to describe a specific task).
That said, if you really get to the point where you understand programming, you'll have a very valuable skill set - one that can't be outsourced. Programming is much more than writing source code. I suppose some people argue that I'm describing "software engineering" and not "programming" but I think part of the problem with software these days (for instance, go read thedailywtf.com) is because people no longer emphasize the importance of understanding and just want to get source code out the door as inexpensively as possible.