Back in the magical decade known as the 90’s I got my first graphing calculator. It was one of the Casio FX-7000 variants–I don’t recall which one exactly, but I do clearly remember that it had 422 bytes of memory to be used by programs. While I wrote some programs to do mathy stuff, most programs were games. I think the first game I wrote for the calculator was a number guessing game where the game would generate a random number and the player would enter guesses and be told it the actual number was higher or lower. There were various other games along the same vein. Then I started coding with a friend and things got “Dangerous”.
My friend Jed had a Casio graphing calculator too. His was newer and fancier and had more memory, but it used the same programming language. One day (I think during French class), he showed me his new game “Dangerous Field”. It was a text adventure game in which the game play went something like this:
DANGEROUS FIELD U R IN A FIELD WUT? > N U R IN A FIELD WUT? > E U R IN A FIELD WUT? > N U FALL IN HOLE U DIE 3
Zork it was not. In Dangerous Field you were in a field and could go North, South, East, or West. After a random number of moves, you fell in a hole and died. The “score” was the number of moves made. There was no terrain or scenery apart from the field, there was no possible strategy, and there was no way to win. But it was a start.
We made new versions of Dangerous Field adding various features such as a map stored as an array defining a path the player could potentially follow to escape the field. Other games were added to the Dangerous series including “Dangerous House” and “Dangerous Cave”. Combat was added as well as rudimentary graphics–all within 422 bytes.
In the years since then, I’ve written a lot of code in various programming languages, but never have I been so concise. My next calculator was an HP48G (which I still regularly use and is currently sitting on my disheveled desk) with 32KB of RAM so I had enough room to write whatever I needed. A full computer obviously has tons more space, and even the toy apps I’ve written for a space-constrained smart phone have been measured in megabytes. So now, whenever I think about the constraints surrounding coding, I remember Dangerous Field and all that was crammed into 422 bytes.
The first book is a 45 year old Le Petit Prince in the original French. I believe I stole it from my parents’ home and it most likely was previously claimed by my mother or sister. I remember as a kid reading an English translation (which my parents probably still have along with another French copy) and enjoying the story while marveling that my parents and sister could read it. Later when I was studying French I read portions of the text and experienced the story in new ways because I was forced to slow down (and often read it aloud).
When I saw the word “Triby”, my mind jumped to a classic Star Trek episode and I imaged Captain Kirk and a bunch of fuzzy things. A quick search revealed that those are “Tribbles” and that the Triby is very different, but the similarity in name grabbed my attention enough that I put forth to answer the question, “What’s a Triby?”
To me the Triby looks like a toy radio for children. It has a magnet on the back so that it can be attached to a fridge. The buttons are also have a toy-ish appearance. The screen is a small e-ink display–probably to reduce power consumption (the battery lasts about two days on a charge). The neatest physical aspect of the Triby is the mechanical flag that pops out of the side when a new message is received.
Last week Boy #2 used his hard-earned savings to buy a little quadcopter. With practice, he has become rather adept at piloting rather than crashing and has had a lot of fun. But what intrigued me the most was that it contains a camera which can take still pictures or video. Since I didn’t think it would be nice to take over the boy’s new toy and since it is was my birthday, I decided could buy my own toy.