I do enjoy programming from time to time. Here’s what I’m currently working on, as well as some of the stuff I’ve done in the past.


XorbZ
XorbZ is my latest programming project. I’ve been working on it for several months now, and have registered it with SourceForge. Like Lasers!, XorbZ is an open-source game. Work began when I became hooked on a game called Assimilation. Unfortunately, that game only contains 10 levels, and my coworkers and I became bored of them quite quickly. It doesn’t allow you to design your own levels, so I determined I’d program a similar game myself which would allow me to design my own levels. At this point, the game is playable, though there are still many bugs to fix.Take a look at http://xorbz.sourceforge.net


Lasers!
Lasers! is a game I’ve been “designing” for quite some time now. The original idea was conceived of back in 1995 as an exercise in assembly language programming. I got a fair amount accomplished in the original game, but coding in assembly was slow, and I accomplished the goal of learning assembly long before the game was actually finished.I later started the project up again, but this time as an exercise in C++ under Linux. Things progressed well, I’m pleased to say. The project has it’s own web site, or you can learn more about the project at www.sourceforge.net/projects/lasers.


Mini-Breakout
Remember the old Atari game Breakout? As one of my original forays into the programming world, I took it upon myself to write a version of the game on an old Apple II+. It quickly turned into a code-reduction exercise, trying to squeeze the program into as few lines of code as possible. I eventually got it down to only two lines of Apple Basic, a feat which earned it publication in the September 1988 edition of Nibble magazine as a two-liner contest winner. Pretty cool for a teenager. If you have an old apple II lying around (or an emulator), here’s the source code. Note that you’ll have to type in each line without spaces or carriage returns, and substituting the “?” operator in place of the “PRINT” statement in the second line in order to get it to not overflow the keyboard input buffer. *Sigh* …those were the days. 😉