Hello. My name is Gary Beebe, I'm a software engineer and web developer, and this is my homepage. Here you will find a number of things ranging from games that I've written, blog posts about games that I'm working on, art work for other sites or businesses such as logos, and links to sites that I have designed. In other words, this site basically serves as my personal portfolio as well as a place for me to show off.

This is my 2nd upload for my Game Development Discipline series. I wasn't able to work on it in the last 3-4 weeks, so I forgot where I left off, and what needed to be done. A good lesson on why it's important to keep a dev log. Point taken. I took this night to complete the game in haste so I could move on to the next game. Anything else that needed fixing is completely forgotten, hopefully nobody will notice any glitches.

Last night, I was kinda being "blah", trying to dig up some motivation to work on my Tetris Clone. I started playing what I had accomplished, being mindful of all the things I had to complete, while taking note of the kinks and bugs that I was discovering. Mainly, it had seemed that the game wasn't speeding up the further I went along, like it was supposed to. During that time, a friend stopped by. After about five minutes of straight play, trying to notice a change in speed, my three year old had an emergency potty request (command), I put my visiting friend in control of the game, so I wouldn't lose any of my in-game progress.

Being an independent, as in a "solo", game developer, that was probably the best thing I could have done. I was immediately bombarded with questions like "Does it do this?", "Shouldn't it do this?", and "Is it this broken?".

What part of "I'm "working" on a game" don't you understand? Actually, having a game tester, I realized, that has no knowledge of game programming is a pretty paramount tool. I spent the greater portion of that night fixing the things that he noticed were broken, and added the things that he complained the most about, banging out a bunch of code, going from "blah" to half way done.

The whole ponit of finishing a game is to let the world see it, right? So, why not let someone give it a go before it's complete. You don't need a professional game tester, friends and family members will do... Ok, maybe keep it away from extended family and in-laws, once they realize you have "the gift", they'll start asking for favors.

Snake is the first of my Game Development Discipline series. It's simple enough to play, at the beginning press 1 or 2 for 1 or 2 players. Player 1 (blue snake) uses the arrow keys, player 2 (yellow snake) uses the WASD keys. For single player you just try to beat your own high score. The goal of 2 player is to win the best of 5 games (no score is kept). Just like classic Snake, red apples makes you grow, but here there are also green apples that make you shrink, as well. My son, age 7, loves playing 2 player against me.