Prototypes exist to help development teams answer a few questions. Is this feasible? How long might this take to develop? What pain points are there going to be? Are we on the same page with the customer? As such, code and design quality will suffer. After all, we're trying to build things fast and get answers to our questions.
In the classic book The Pragmatic Programmer, the authors suggest that certain details can be ignored including 1. Correctness, 2. Completeness, 3. Robustness, and 4. Style. However, it should be more nuanced than completely neglecting these four points. Depending on the project and the intent of the prototype, you may invest more in one of the areas.
Big problems can occur when the development team and/or customer fall in love with the prototype.
What do we do about CDNs in DoD/Enterprise environments?Read More >
Some time ago we contracted a vendor to develop a small application for us. After multiple setbacks throughout the project, I received a phone call.Read More >