I learned on the TI-83. You learn skill-sets in chunks. First it was menus. Then holy-shit, variables. Things kinda just go from there. You never as much lear

I learned on the TI-83. You learn skill-sets in chunks. First it was menus. Then holy-shit, variables. Things kinda just go from there. You never as much learn programming as you "absorb" it. This includes things like syntax, approach, mind-set, etc. This goes for every language, especially if the idioms are different. Come up with a cool project with small scope and a discernible "end goal," and do whatever it takes to get there. You'll learn more along the way than you expected to. I learned more about call-stacks, memory management, and pointers in front of MS VC++6 compiler and runtime errors than I ever thought I would when "making a game." Its like learning any other language or math. Learn and understand and atom, and use that to understand another. Its definitely cumulative and you can't learn it "front-to-back" as much as it is in "bits and pieces." Good luck! (If its any help - this is the order I learned things in. Not documenting my age or how long I spent learning it as it spans more than a decade) HTML TI-Basic (TI-83) Visual Basic C++ CSS (finally stopped using homesite) Java Python C PHP ActionScript Ruby Javascript