2 ms·

Especially with Rails as rapid prototyping language this is kind of a bad advice IMO. Usually the prototype already will be the base of your application and we

by herbst 10y ago

Especially with Rails as rapid prototyping language this is kind of a bad advice IMO. Usually the prototype already will be the base of your application and we both know you will never get rid of all the dept you could build that way

albeebe1 10y ago
My use of prototype was probably a poor choice. Not sure what is better replacement.
- herbst 10y ago
  I see where you are coming from but this just does not fit the way a typical rails coder operates.