Comments on: The amorphous project http://xalthorn.wordpress.com/2008/06/02/the-amorphous-project/ a blog to collect Xalthorn's random thoughts Sat, 28 Mar 2009 13:17:05 +0000 http://wordpress.com/ hourly 1 By: Xalthorn http://xalthorn.wordpress.com/2008/06/02/the-amorphous-project/#comment-146 Xalthorn Wed, 18 Jun 2008 12:05:32 +0000 http://xalthorn.wordpress.com/?p=47#comment-146 Yep, and all too often rather than developing a single game/project with a definite plan and set objectives, we find ourselves creating a wildly dynamic 'engine' that can accomodate this and future projects. Of course, because this 'engine' starts to gather a rapidly increasing feature list, it will never be completed. What we should be doing, I believe, is getting straight in with a project. Give it set objectives, realistic targets, and so on. When the project is finished (or at least at version 1.0) review what was done, how it was done, how it could be improved for version 1.1, and how it could be adapted for future projects. This way, not only do we get a completed project, but we start building up a library of routines and methods of working that can eventually form a dynamic project 'engine'. After all, if we were being paid to work to a deadline and given an objective and parameters to start with, we wouldn't have time to mess around adding things that weren't asked for and weren't needed. We would complete the project as asked and make notes, documenting what we did and what we learned from it to make our future projects quicker to develop. Yep, and all too often rather than developing a single game/project with a definite plan and set objectives, we find ourselves creating a wildly dynamic ‘engine’ that can accomodate this and future projects. Of course, because this ‘engine’ starts to gather a rapidly increasing feature list, it will never be completed.

What we should be doing, I believe, is getting straight in with a project. Give it set objectives, realistic targets, and so on. When the project is finished (or at least at version 1.0) review what was done, how it was done, how it could be improved for version 1.1, and how it could be adapted for future projects.

This way, not only do we get a completed project, but we start building up a library of routines and methods of working that can eventually form a dynamic project ‘engine’.

After all, if we were being paid to work to a deadline and given an objective and parameters to start with, we wouldn’t have time to mess around adding things that weren’t asked for and weren’t needed. We would complete the project as asked and make notes, documenting what we did and what we learned from it to make our future projects quicker to develop.

]]> By: Cameron http://xalthorn.wordpress.com/2008/06/02/the-amorphous-project/#comment-144 Cameron Tue, 10 Jun 2008 03:17:05 +0000 http://xalthorn.wordpress.com/?p=47#comment-144 I am guilty of this on many accounts myself, sometimes even after I realize it and sit down with a "new" plan for the work in progress I get side tracked building nice to haves and trying to create hooks for eventual features rather than just finishing the present features. I guess it is all a learning experience and something that can only be learned by experience. :) I am guilty of this on many accounts myself, sometimes even after I realize it and sit down with a “new” plan for the work in progress I get side tracked building nice to haves and trying to create hooks for eventual features rather than just finishing the present features.

I guess it is all a learning experience and something that can only be learned by experience. :)

]]>