21–30 of 70 posts
Later C,C++, python, objective C..., I think understanding what the computer does with every line gives you an advantage. Some things become obvious to you but not to other programmers without hard assembly experience.
Kindergarten, late '80s.
I started at 7, and I though that was on the early side.
Early 80's: C64 BASIC & 6502 ASM =)
[1]: http://en.wikipedia.org/wiki/File:ComputesGazetteProgramPage...
While I'd hate to develop anything in VB these days, it did kick off my interest in software development. Especially when my friend was into it as well so we'd make stuff and share it with each other.
Java developer by trade these days, and I use Ruby or Objective-C for personal development.
In BASIC (the horror) when I was maybe 6 or 7. I tried making text adventure games by writing out every if/then branch explicitly...
I was lucky enough that my grandparents bought me one of those computers that hooked up to my TV, and it had a BASIC interpreter on it. I still have the manual...
There shouldn't be an apostrophe between the number and the 's'. "Will learn in the 10s" should just be "10s", as some people may have already started programming in the past 12 months
The usual answer to the date controversy is that since there wasn't a year 0, each decade must be 1-10, so the 10s start in 2011. I'm comfortable with saying, instead, that the first decade had 9 years and the first century 99 years, and so on, but other people seem to object more. :)
