Hacker News Reader

I love prototypes. You have the joy of the blank page, the freedom of the choice of COTS. You can ignore requirements that would introduce complexity. You do not need to follow the coding rules that impose verbosity. As a result, you can build something simple you can be proud of.

The prototype is a showcase that allows to show how development could be faster if there was less stupid requirements and less coding constraints.

View on HN

Every problem is easy if you oversimplify the requirements.

The purpose of a prototype is generally to tackle one or two of the difficulties (among UX, thread architecture, dataflow, performance, complexity of data, encoding/decoding, robustness...) while ignoring most of the others. The other requirements will come back, but at least you have a good solution of the most problematic ones.

Reply on news.ycombinator.com