This post originated from an RSS feed registered with Python Buzz
by Rod Hyde.
Original Post: a nascent pattern: know what is unknown
Feed Title: The landscape.
Feed URL: http://www.bloglines.com/blog/RodHyde/rss
Feed Description: The technical landscape through the eyes of an occasional indie games programmer who now uses Python as his language of choice.
I was thinking how great it would be to have a "pluggable" architecture, in which aliens and their behaviours could be added without having to hack apart the main class. Indeed, it has become very clear to me exactly how to do it. But, much as I would like to do it for aesthetics, I am not going to do that now, because it doesn't contribute towards the goal, namely, "finishing Corvids".
Strangely enough, I may go back and do it once I have finished the game. Why? Because I would like a pluggable architecture in my next game and whatever I create for Corvids will almost certainly translate over. The idea is that I don't want to be thinking about more than one unknown at a time. As I already know what Corvids should look like, the architecture is the only unknown.
In fact, thinking about it, that was my motivation for writing Corvids in Python ... Python was the only unknown. Do I detect a pattern emerging?
Previous Topic
