> I decided that it was my game and there was nothing wrong with continuing development on it after a four-decade break--especially since it's unclear whether anyone managed to get it running in 1981.
The TRS-80 was my first home computer. I do vividly remembering typing in the whole of Artic Adventure, cursing that I had made a mistake, and painfully checking over every character to find I had put it in identically.
However, bug-checking a typed program was also a common experience. Most of the BASIC games I re-typed from magazines had unplayable flaws in them, so I did actually manage to get it running... Eventually.
Debugging typed in programs is how I learned programming. Actually understanding the code I was typing in instead of trying to get everything typed in perfect made debugging so much easier, plus I could make my own customizations. I only typed in a couple of text adventures because the process of typing them in often gave away most of the mysteries in the game, which wasn't an issue with action type games.
It was the only practical way to learn programming if you didn't go to college. The manuals for those early micros were somewhere between useless and wrong most of the time, magazine articles (and 101 basic computer games of course).
Somewhat unrelated to that, after I had learned programming and been to University, the most educational experience I had was re-compiling sources for software on Unix machines that weren't quite mainstream. Porting TeX / LaTeX to a Pyramid was super educational, plus a fascinating insight into the mind of Donald Knuth.
I don't remember a lot of details, but from memory the software came on a big reel of tape and you dumped the tar archive off it, unpacked it and tried running the Makefile.
This was around 1988, 1989 and the Pyramid was already obsolete but the organisation had a huge investment in it as a 100 user machine with serial terminals so we had to make do.
First thing was to get the tangle and weave programs running. The header paths and library locations weren't completely standardised and even the function signatures were different between machines. There was no "configure" back then, so it was a case of digging through the the compile and link errors, fixing what didn't work and trying again. Once tangle and weave were running the job got a bit easier until it came to the PostScript output program which was a bit of a law unto itself, but I might not be recalling that part correctly.
Once the tangle/weave steps started working, the Makefile assembled everything and install from there was fairly simple. The bones of TeX were written in an intermediate language and needed the tangle/weave pair to turn it into something functional. To fix my adaptations required developing a passung knowledge of that intermediate language, which was half comments and half expressive code. Once I got my head around it I thought it was fascinating but not terribly practical. Then again, I'm no Knuth and never built anything as cool as a computer type setter so what do I know.
There were a few times that tangle and weave did something weird, but mostly that was my adapted code not working as expected. A few revisions sorted those out quickly.
This must have been right at the tail of that era of Unix though, the Sun workstations were easy to get TeX and LaTex for pre built.
The learning experience of trawling through include files looking for the right functions and adapting calls to make them work on that Pyramid was invaluable as a developer later on, not for the Pyramid knowledge but as an education into unix.
Now of course you can copy and paste your error into google and likely somebody solved the problem already. Back then we had the include files and occasionally usenet. It wasn't necessarily harder to get things done but it required patience and time.
Thanks for sharing! That matches what I've read from other sources. Sounds like an educational experience indeed… a lot of things we take for granted today.
I was lucky in that my father worked for National Mutual (today they're AMP Limited), and so I ended up as the first person in my school to have a personal computer.
Without that, and the encouragement to experiment on the machine, I very much doubt I would have ended up as a programmer.
Both. National Mutual were a major investor in Tandy, at the time. They also expected their staff to take home work, and so supplied every manager with a computer.
Our school had them too, but no one had one at home. We had Apple IIs, Vic-20s, TI-99/4As, etc. Was Tandy just really good at selling into the education channel?
The TRS-80 was my first home computer. I do vividly remembering typing in the whole of Artic Adventure, cursing that I had made a mistake, and painfully checking over every character to find I had put it in identically.
However, bug-checking a typed program was also a common experience. Most of the BASIC games I re-typed from magazines had unplayable flaws in them, so I did actually manage to get it running... Eventually.