What is it that you hope to accomplish? Are you learning a programming language just to learn it or are you hoping to develop a particular application? Will this be self-learning or will you be taking a class? What platform are you developing for (OS X vs. Windows vs. ???). Do you want to eventually do this for a living?
I'll assume based on the forum here that you want to write programs on a Mac and for the Mac. If you want to automate tasks or whip up a little application I would start with
AppleScript. (Yes,
AppleScript.) High level enough to be understandable, practical enough to be useful for every day tasks on your computer, really a good way to get your feet wet. It comes with your Mac.
If you are looking for something more formal, a class or a friend who programs will help immensely. There are online tutorials for all kinds of programming languages, but there tend to be tough topics to grasp at first and someone who can look and see what is wrong (not fix it necessarily, just tell you where a mistake is) can be the difference between getting started and quitting in frustration and confusion. If you have a friend who knows C or if you have access to a Java class, that may be the most important consideration. Don't underestimate this.
As to which language beyond AppleScript... Objective-C is really only for OS X on the Mac these days, but likewise, most new Mac development is written in Objective-C and one of the Mac programming frameworks like Cocoa. If you are only interested in Macs then start with Objective-C (it comes with your Mac
). If not, I'd look at C or a "baby" C++ class or maybe Java (C++ minus minus, C++ with the dangerous -- and powerful -- features taken away). Lots of Windows programming used to be done in VB, but now its mostly done around the .Net ("dot net") framework either in VB.Net, ASP.Net or C#.Net. Either way, once you learn procedural programming and get used to working with objects it'll be easier to move to other languages.
The last thing I'd say is that a programmer/developer spends a lot of time at work
not coding but deciphering requirements, designing solutions, working with project plans, debugging things that ought to work but don't, writing documentation and filling out status reports. I can't tell you how many people I've known over the years who were good programmers but just couldn't take working on a development team. Just be aware that there is a lot more to most programmer jobs than writing new code.