Well... the <i>very</i> first coding I did was on a Bally Arcade game console. One of the "games" you could get for it was a BASIC environment, so I'd run that and type in some BASIC programs from some book or magazine or whatever. I didn't actually go very far with that though, because there was no keyboard and you had to do all the typing by manipulating an on-screen keyboard with the game paddle thing. Which TBH, kinda sucked. Anyway, all of this was probably about 1988 or 1989 or thereabouts.<p>Fast forward to 1993 or so, I was at Brunswick Community College, and took an "Intro to programming logic" class and some other "Intro to Programming" class. I also built my first real PC (a 386DX/40 system with 1MB of RAM, which I later upgraded to a WHOPPING 4MB so I could run Borland C++). Anyway, I bought a copy of Herbert Schildt's book <i>Teach Yourself C</i>, downloaded a C compiler from some BBS (I didn't have Internet access yet at this time) and started learning to code in C. I consider this the real beginning of my programming education.<p>Fast forward to 1995 and I'm at UNC-W and taking another introductory level programming class, and it's about the first or second week of class and the instructor (Dr. Adhar) gives us some lab assignment to code in C. I code it up and wait as he's coming around checking on people. He gets to me, looks at my code, and in this awesome sing-song / rolling accent of his (I think he was from Pakistan or something like that) he goes "Aaaah, I see you be using techniques I no teach yet. Very good. Carry on." And it's been a continual process of learning more and more ever since.<p>I went from C, to C++, to Java, to Groovy, and mixed in splashes of Python, R, Octave, Kotlin, Prolog, LISP, etc. over the years. These days if I'm writing code it's usually either in Java, Python, or Groovy.