通过

Prototyping: Do it right or get it done?

  • 项目

Given that prototype code has a way of becoming ship code and that one usually doesn't have a whole lot of time to play with a prototype, should one take the time to "do it right" or just mock up as many features as you can in your timeframe? 

 

Hard-coding resource strings:  yes or no?

Globalization: yes or no?

Performance investigation:  yes or no?

 

What is the priority list of things to do right in a prototype?

Comments

  • Anonymous
    August 04, 2003
    Heh, do it in Director so the prototype stays the prototype. :-)
  • Anonymous
    August 04, 2003
    The comment has been removed
  • Anonymous
    August 04, 2003
    Depends on the customer. Last time I created just a "prototype" in a very short time. I thought I was just providing something that looked good and did what it was supposed to - worked with other customers. It needed performance optization, etc. etc. My mistake - I should have done it right. Instead of just something to show the customer it was used in the final product - not by me, I wanted to re-write it the "right" way. For most of my projects performance is highest priority.