I’ve been pondering this question, and it really amazes how much one can accomplish in just 21 hours. The box stacking mini game didn’t take much of my time, but I have poured unbelievable amount of hours to making of multiplayer game framework, mostly for Edoiki. Initially I planned that the Edoiki game would be produced in just few months, but then various events occured (such as lead programmer leaving the house, getting lots of new ideas, chancing the core network code and so on) which have delayed the project for over half a year already.
All the things haven’t necessarily been bad: even though completely re-coding the core network code did took time, there has been benefits as well. It’s now faster to try new things and the server-client architecture seems quite solid. Also, while the programmer left, it has given me chance to learn more coding. There are open issues in Edoiki development: at the moment I’m pondering publishing the game in Episodes. That way I might be able to cut down some features and actually get playing the game faster. This is one open issue, which will get answered soon. I want the game out. All these decisions will have an impact on the project progress.
It’s amazing how much you can accomplish in just few days. And even though a game would take 21 months to produce, it must be finished in small steps: doing 21 hours after 21 hours. If you keep taking baby steps one after another, eventually the game will be finished.
Worrying about how badly deadline was missed, or worrying about the “upcoming workload” is useless. It only gives you a bad feeling and doesn’t help progress. Instead, concentrate on what you can do and take those steps forward. One by one. That’s the only way to reach the place where you want to go: by taking action.