4 ms·

Why would build a prototype to only throw it away? This seem naive.

• Zikes 13y ago
  I think the prototype in this case is more to flesh out the idea and its associated functions, without concerns for code quality or security. It would help a lot in building the road map for an application, but you definitely wouldn't want to use any of it in production.
  • 1qaz2wsx3edc 13y ago
    Some frameworks are designed to help with this step though. For instance: Rails has scaffolds & generators, angular.js has directives (plain old html views you can open), html itself can be used for mock-ups (and there are plenty of others as well). Specifically, why build a partially functional prototype only to throw it away for another framework down the road. It seems naive to me, because the effort you put into the prototype is mostly dropped (except for high-level mental models). Rather then building a throw-away prototype, I think it's better idea to build a prototype you can refactor and improve, with one set of tools.
• 32bitkid 13y ago
  you and I have very different definitions of "prototype"
• tudborg 13y ago
  You need to go look up "prototype" ;)
• xiaoma 13y ago
  1) Seeing things in action often clarifies my design. 2) You can build things really fast with Meteor. 3) After you know what you're doing you can develop the robust version much more quickly. This time savings is often significant. 4) Since Meteor is built on Node, you don't throw everything away. You can actually keep quite a few functions and nearly all your handlebars intact when you port to the final project. I'm not saying working this way is for everyone, but it works well for me.