ZZT! It had its own in-game editor and scripting language ZZT-OOP, which blew my mind as a kid. That was the gateway drug to Flash and ActionScript, HTML, IRC bots, Minecraft mods, and more. Self teaching by building something fun and exciting always worked the best for me. Back when coding was for fun and not money :-)
Ask HN: How did you learn to code?
51–60 of 89 posts
Re: Ask HN: How did you learn to code?
#52neopets was definitely a factor, who else? And "hacking" school computers, windows use to let you make folder backgrounds with html, could do some funny stuff.
Re: Ask HN: How did you learn to code?
#53Re: Ask HN: How did you learn to code?
#54Then really learned Python in 2010s trying to solve a real-life problem - had to scrape an ecom website, used Scrapy. Now it's Go, quite complex projects, about to launch our SaaS startup.. took a while..
Re: Ask HN: How did you learn to code?
#55From there on I was always learning faster and more at home as a hobby, I was mostly ahead in school. A friend and classmate and I coded so many different projects during that time (2D terminal game, PHP forum, PHP CMS that was actually productive for a few years, thereby also learning how the internet worked).
It's just crazy how lucky I got to be interested in this thing at the right time. "Back then" I feel you got so much more time to learn something well, mostly because things weren't changing at crazy speed.
Re: Ask HN: How did you learn to code?
#56Re: Ask HN: How did you learn to code?
#57Re: Ask HN: How did you learn to code?
#58https://winworldpc.com/product/turbo-pascal/6x
System specs: https://pastebin.com/raw/yHqGgxhx
Re: Ask HN: How did you learn to code?
#59Re: Ask HN: How did you learn to code?
#60Slowly worked out how navigate the system, then tried running the various built in things I found
One of these was QBASIC. Started reading through and messing with the example games which were part of the built-in QBASIC in MS-DOS
Reverse engineering how they worked gave a lot of the core concepts (variables, loops, procedures)
After writing a few (very) naff text adventures I stumbled across the intriguingly named "DEBUG" tool
Used debug to step through some of the other built in MSDOS utilities and try to work out what the mysterious symbols were doing (how I learnt assembler and machine code)
Later when I finally found BBSs I started debugging/disassembling some of the BBS mini-demos which were ubiquitous those days, which introduced me to manipulating graphical memory etc.. The smaller size of these, and fact that they were generally coded in assembler was much more useful than reading through compiled code
I do not recommend writing assembler in DEBUG, but wouldn't trade in the learning I got from exploring a total black box with no references or learning resources (beyond time and curiosity)
Felt like doing alchemy