Should I focus on code quality with rapid prototyping?

Question

If you quickly prototype functions, do you really have to worry about quality and code optimization?

Answer 1

Looking back at the number of times that "prototype" ended up becoming a product, the answer would be yes.

Do not forget that you are not only prototyping this feature, but also prototyping the design.

Answer 2

Yes to quality. No for optimization. This question must be a wiki community.

Answer 3

.

Answer 4

, . , . , , , , , .. , , , .

Answer 5

. , , , ( , , , ).

, , , ? , .

, , , , . , . , FALSE .

, - , . , , , , , /.

You may be worried about optimization later - see this description a huge win. I got the transition from MFC CMaps to STL while working on a hobby project that analyzes some Apache log files. This was done after I had the initial concept, and only when it became obvious that there was a performance problem.