Best practice for prototyping?

Question

During prototyping, to what extent do you throw best practices out of doors in favor of breaking the code and fixing it? Provided that the code is not intended for full storage.

Add: I am working on a rather large semi-working prototype made in Python to define an interface for an embedded application. I know that the code is not intended for use in production, but still it annoys me that the quality of the code base is steadily decreasing with the number of changes made.

Answer 1

It depends on what your prototype is trying to prove. Do you prototype the user interface for ease of use and demonstrate to customers or use prototypes of architecture?

If I prototype the user interface, then I will throw away everything as soon as the concept goes through iterations and is proven.

If I prototype the architecture, then the final code will be in line with best practices and will be used.

However, it is surprising the number of prototypes of hacking workers that end in full production due to lack of time or budget. If your intention is to ensure that the code does not end in production (i.e. the prototype user interface), then a screenshot layout may be useful, rather than their code.

Answer 2

, - . . , , , , , . . , , , . .

Answer 3

"" (.. , " " ), "-", .

, , "" "WheelCount", "DoorCount" Hashtable, , , Car.

, , , , ( "" ).

- " ", ... , , , , ", , .

Answer 4

( "" ) . , . , , ( , , ).

, , , , , .

Answer 5

. , , , .

Remember that a prototype is just a tool for getting a customer response. (Yes, I like it, or why did you put this option there?).