advice on keeping it small

#1 Well writing a design document can certainly help but I find that approach alone too rigid. I find it helps if you split your game up into the features you expect then think about how to get those features done individually, assuming they're not intricately linked somehow.

I like to prototype each feature and work out how I'm going to do it, none of which are actually writing the game. Also, try to prototype the hardest feature first although that's not always easy to determine until you've tried.

You'll soon discover which features work/don't work, which are too hard and perhaps some nice twists on what you originally designed will emerge.

I would certainly not use one base and try to experiment with that as it'll soon degenerate into a mess.

So I guess the idea I'm saying is to just try to prototype first. Perhaps you can try to use TortoiseSVN/VisualSVN Server on your PC and create a local repo with a base for your prototypes. This allows you to create branches from that base which you can modify and/or roll-back as you're experimenting.

#2 One thing I learned; if your code gets exceptionally long for what seems a simple principle, start over.

#3 You have your answer after your question ;)

But to learn a game must become bigger and more complex at some point. Try to reach that point making mistakes and learning from them.

#4 A complex system that works is invariably found to have evolved from a very simple system that works.

John Gall, Systemantics, 1975

#5 I think the next part to that is also apt:

Quote:
A complex system designed from scratch never works and cannot be made to work. You have to start over, beginning with a working simple system.

Great quote btw.

#6 Definately keep a document with all of your great ideas. One way I try to keep things simple is to aim to make multiple demo's. For breakout, find the aboluste minimum you need to make it playable, then make a build, share it with friends. At that point you can sit back, think about what you'd like to change. Because you have released a copy that is playable, you can go back, re-factor code, make any change you need, add a few features, then make another release. The act of building the game, wrapping it in an installer, gives you the closure and the allowance to either go back and make it better or move onto another small project. Don't put any pressure on yourself to make this the next AAA title. I've made demo's that people didn't like, I take my lumps, and try something else.