Feb-07-2017, 10:47 PM
Prototypes are often crap-code. Implementation need to be built to last. To be extended, improved, and bug-free. Prototypes are often built, not with robustness in mind, but getting something minimally working quickly. They're often designed poorly (if designed at all), bugs are ok and often not tracked.
Sometimes, a prototype is just an early revision. It might be designed well, any bugs are tracked, but it lacks features and may have bugs, but could be shown in a demo. This second kind is less common. For the first kind, the code should probably be wiped and programming start fresh.
Sometimes, a prototype is just an early revision. It might be designed well, any bugs are tracked, but it lacks features and may have bugs, but could be shown in a demo. This second kind is less common. For the first kind, the code should probably be wiped and programming start fresh.