Prototyping is a learning experience Its value lies not i | SeasonedDev
Prototyping is a learning experience
Its value lies not in the code produced, but in the lessons learned.
You can prototype anything that carries risk, unproven, is absolutely critical to the final system. It can be:
Architecture
New functionality in an existing system
External data structure
Third-party tools or components
Performance issues
User interface design
When building prototypes you should focus on specific aspects. These are the details you can ignore:
Correctness - use dummy data where appropriate
Completeness - isolate the concept you're proving
Robustness - be specific, error checking may be excessive
Style - after all, you're going to throw the prototype away anyway
Properly used prototypes can save you huge amounts of time, money, and pain by identifying potential problems early in the development cycle - the time when fixing mistakes is both cheap and easy.
