3 ms·
Advice from a long time ago that took me way longer than it should have to understand fully: "Always throw the first one away." I now consider the entire firs
by bigiain 15y ago
Advice from a long time ago that took me way longer than it should have to understand fully:
"Always throw the first one away."
I now consider the entire first prototype to be part of the "working out the design" process, and all the code written for that is considered disposable (quite often I write a prototype in a different language to the intended delivered product, partly to ensure I throw the first one away, but when I'm honest with myself - at least partly 'cause I enjoy rapid-prototyping in Perl.)
- barefoot 15y agoAn important corollary to that statement is: "And never show the prototype to non-developers".
- debacle 15y agoThis is probably my biggest fault. "So I whipped together a quick API integration yesterday evening..." "Oh, so you're almost done then!"
- beagle3 15y ago... except those who are the users of your system. No product design survives first contact with users, and it would be a waste of time if you do not use feedback that the first prototype can get.