GeekStack is recruiting playtesters for our online trading card game with a science and technology theme. If you're interested, sign up here. Thanks!
Weekly Update 8/19/2009
Posted on | August 19, 2009 | No Comments
The contest to design the first card is going well. There are several designs so far including a couple that really are spectacular.
I’ve had a couple people get in touch that are interested in working with me. I’ll talk more with them over the next few weeks and I might walk out of this with a cofounder!
The last piece of exciting company news is that I’ll be at the TechCrunch50 conference on September 14-15! I’m not presenting – I considered entering at one point but I knew I wouldn’t even have an ugly demo ready by then, let alone an attractive, professional looking demo. I’ll just be schmoozing, making contacts, and looking for partners and maybe investors. If you’ll be there or are interested in meeting up while I’m in San Francisco, send me a message or Tweet me (@geekstack).
WARNING: Particularly programmery-nerdy parts ahead.
This week I started the 3rd rewrite of the core game engine code. Each of the rewrites have come when the assumptions I made ran out of room to maneuver in and I had fairly well worked out the problems related to a certain area of the code. For instance, the v3 that I just retired was mainly about moving cards around within one player’s zones and executing some of the actions on those cards. I worked out a lot of kinks in that area but got to the point where I would have to change a lot of code to implement my newest understanding of the problem. Rather than go through the tedious process of changing all of the code to reflect that, I prefer to start with a clean file and write code that incorporates all of the parts of the problem I have seen since the last rewrite. This gives me a chance to implement pieces that I postponed, in this case how to include multiple players in a game and how the system will track multiple games at once.
Even though this sounds like more work, it usually ends up taking the same time to rewrite as it would to edit. Plus, when I’m done rewriting, I have code that’s shorter, cleaner and more consistent, and includes more functionality. Since I’m responsible for all of this, any time I can add design and understanding to reduce complexity and remove code, I need to.
Delicious
Comments
Leave a Reply
