KISS (Keep It Simple Stupid)
Make sure that the current section of code WORKS. If its slick and doesn't work, it doesn't do any good. In the words of my Assembly Language Professor (Yep, was a long time ago
), "When all else fails, use Brute Force." Once you have a section of working code, then you can 'slick'en it up.
Avoid the 4 P's (Piss Poor Prior Planning).
Everthing is ultimately dependent upon your preparation. Decide early on what you want & how you want it, and, don't give in to Feature Creep. Maintain your objective, add features later.
One other thought....Graphics is window dressing, mechanics will make or break the game. Make sure your (game) mechanics are solid, and the graphics can be added/prettied up later. This relates directly to the 4 P's.
[ 30 November 2001: Message edited by: Spyder ]