Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
While prototyping, to what extent do you throw best practices out of the door in favor of code-and-fix hacking? Granted that the code is not intended to be kept in full production.
Add: I am working on a rather large semi-working prototype made in Python, to figure out the UI for an embedded application. I know that the code is not intended to be used in production, but still it annoys me that the quality of the code base declines steadily with the number of changes done.
It depends upon what your prototype is trying to prove. Are you prototyping the UI for usability and to demonstrate to clients or are you prototyping an architecture?
If I’m prototyping a UI then I’ll throw away everything once the concept has been through iterations and proven.
If I’m prototyping an architecture then the final code will conform to best practices and be usable.
That said, it’s amazing the amount of hack job prototypes that end up in full production due to time or budget constraints. If your intention is for the code to not end up in production (ie a UI prototype) then it can be useful to mock up screenshots rather than code them.