A good, quick, on-the-point prototype is very likely to be a code mess, full of hacks and horrendous code writing, especially if it was written by the designer himself. You don't want to end up with that code in the final project. When a prototype works and all the questions have been answered, it's time to start from scratch. Now is the time to build those systems and allow an engineer to design the code properly. Again, the mirage of using the prototype code as a base to save time is just that: a mirage. Some time might be saved early on, but rest assured that the first time a problem arises all the time initially saved and more will be lost. This is true even if the prototype ...
Using the prototype as a code-base for the production project
Get Practical Game Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
