4 ms·
The key to having prototypes and PoCs work out okay is to leave some important piece of UX out entirely. Such an approach gets you the benefits of being able t
by NateEag 4y ago
The key to having prototypes and PoCs work out okay is to leave some important piece of UX out entirely.
Such an approach gets you the benefits of being able to explore a problem space with code in a quick, sloppy manner, without any risk of anyone actually deploying what you wrote.
- eurasiantiger 4y agoNever make prototypes easy on the eyes. Use Comic Sans liberally. That way nobody will assume it is the final application which just needs a few touches.
- galaxyLogic 4y agoThat's a great idea. Prototype must look like a prototype
- NateEag 4y agoNot even just "look like a prototype" - a prototype must be _incomplete_. If it's not? You have a solution, so of course it's going to be deployed. The fact that your solution is gonna fall over due to being brittle code is really unfortunate, but it was avoidable if you'd just built a prototype instead of a product.
- mecha_ghidorah 4y agoI mean that's easier said than done in some cases. If your manager wants you to build a complete version of the functionality, just one that is very "quick and dirty" there isn't a whole lot you can do to make it not fully functional short of flat out refusing
- NateEag 4y agoSure, but as noted that isn't a prototype - it's a sloppy product. That's when it's time to have a frank discussion about whether that's really what they want (and maybe to consider whether this project is really what you want to be working on, if it's a common pattern).