That image right up there caused a huge pang of nostalgia in me. It’s the spitting image of our first family computer, an IBM PC, along with the huge set of thick manuals that came with it. The second book to the left, the brown one, was one I became intimately familiar with: the BASIC manual.
Without the internet, loads of stores selling software, or a shareware distribution system between friends, our first couple years of owning this machine was thin in the programs department. We had a word processor, a spreadsheet, and a couple games (like breakout) — but that was it. So as the family member who quickly became the most obsessed with the computer, I turned to making my own games as a form of entertainment. Hence my adventures into the wells of the BASIC manual.
I loved BASIC. It was easy to understand and pick up, although I had no concept of structure and clarity. The manual itself was extremely technical and dry, with each page listing a command, a definition, and perhaps an example. So it was left up to me to figure out how it all pieced together.
I had some help. It seemed like BASIC programming was all the rage with the up-and-coming 80s set, so lots of magazines and books (like Micro Adventures) had sample programs that you could copy and run on your computer. There was lots and lots and lots of typing involved, which I also taught myself (I was a two-finger typist until a high school class broke me of the habit and taught me the proper way to do it). Above all else, it helped me grasp the fundamental pieces to start putting together my own games.
Dang, but I loved making games. I *loved* it. I couldn’t do much with graphics, although I tried hard to figure out ways to make ASCII doodles move (usually via scrolling or screen redrawing). Mostly I made RPGs and text adventures. I did program one series, Spaceship Combat Simulator, which proved somewhat popular with my family. I think the second edition allowed you to choose a hull type of a ship, equip it via store purchases, and take it out for galactic conquest.
These games got obscenely long, too. I was routinely topping 5, 10-thousand lines of code toward the end. I composed my own music and experimented with musical pitches to see if I could simulate speech (I couldn’t). I learned a lot about color pairing, in particular what would make the best background and foreground colors. I had games that would print you off award certificates if you beat them. And I was pretty much the only person who ever played them.
I think I loved all of that because I could envision a game and execute that vision single-handedly. My parents really thought I was going to be a game designer, especially after I started taking programming classes. But something happened in college after I picked up three or four other languages — I lost interest in it. Programming wasn’t fun in and of itself, it was just a means to see my game vision come to life. And it was getting more and more complicated. I could see that we had moved past the point where a single programmer had total control over a project and I had no interest being a coding monkey. Plus, figuring out where you went wrong in one line of code among thousands is a major headache.
So even though I graduated with a degree in computers from college, I stopped pursuing that path a couple years prior to graduation. Perhaps that’s why I started making web pages (again, I could conceive and execute my vision by myself), and later on blogging. I don’t know. But BASIC will always have a special place in my memories, and I regret that I didn’t save the discs that had all of those programs.