>>I agree with Joel; your best bet is to provide a highly detailed >>design spec with complete API, and also provide guidance on what >>components to extend, etc. The downside is that it takes a lot of time >>to do all of this work, and depending on your particular situation, it >>may be unrealistic.
Yeah, had done that, but not in great detail. An API would have been too much. The project was a learning game, and in my mind I couldn't justify spending a huge amount of time writing very detailed design specs, because that could take almost as much time to think about and write as it would be to sit down build the game. I'm very much in favor of abstraction, but they took abstraction way too far, and really to the extreme in my opinion, where the benefits of abstraction are completely lost. Thanks everyone, I'm definitely going to insist on more frequent code reviews with them. I guess I put too much faith in them last time! :) Jason _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
