4 ms·

I feel this directly correlates to the many discussions of the idea being worthless and leads to neglect of the real aspect of ideas being continuous. Given th

I feel this directly correlates to the many discussions of the idea being worthless and leads to neglect of the real aspect of ideas being continuous. Given the timeframe, how can the the added ideas, which are equally important to the original concept minus the original implementation, add the necessary value/execution? Additionally, this is a specific tech choice where I would love the chime of others contributing into this sort of thing, perhaps as a service, where one can choose equally proficient specialists of any stack(coming from a design.ui.idea guy learning ror). I know this is just the efforts of one based on taste/preference which you would choose, so I love the idea.

lucisferre 15y ago
His point about the meaning of prototype is very relevant and on the mark. If the technology stack you choose to prototype matters in any way then it is highly likely that its not a prototype being built. I think it is important to have this mindset when prototyping. Too often I see prototype code make it into production when it should have been thrown away.
- ibdknox 15y ago
  Yes, my goal with using Clojure is 3 fold: 1) Selfish - I really like Clojure 2) I hope more people will see Clojure as a viable language to develop websites in 3) It's obscure enough that most people won't try and turn this into production code. I've seen so many big projects that started that way... I cried when I had to work on any one of them.
  - Tyrant505 15y ago
    I really like your p#3. My additional note applies just to me learning ruby and rails and would hope to take your code further as I progress. I guess what my concern: 5K is fair of course for your level of expertise, but I would love to have it for me to build on and learn on. A bit nieve to hope it would make it into production of course, but additional building and small changes in ui(I know better), model/db changes, logic, from the stack I've been learning will aid in me making a better "prototype", and learning! Perhaps after the initial 2 week job, additional tweeks on hourly or second iteration could be in order?
ibdknox 15y ago
I actually think the timeframe works out perfectly. With two weeks you can have something complete enough to watch people use (or not) what you intend to build a business out of. At the end of the day, it's hard to learn much until you see people use it. A great deal of my time at Microsoft was spent proving that our users didn't do things the way we thought they did. We never could've done that until we had something real. The intent is for this prototype to generate the exact "added ideas" you suggest. Two weeks doesn't seem long enough that the whole world is likely to change out from under you... especially if you have nothing to show people.

lucisferre 15y ago

His point about the meaning of prototype is very relevant and on the mark. If the technology stack you choose to prototype matters in any way then it is highly likely that its not a prototype being built. I think it is important to have this mindset when prototyping. Too often I see prototype code make it into production when it should have been thrown away.

ibdknox 15y ago
Yes, my goal with using Clojure is 3 fold: 1) Selfish - I really like Clojure 2) I hope more people will see Clojure as a viable language to develop websites in 3) It's obscure enough that most people won't try and turn this into production code. I've seen so many big projects that started that way... I cried when I had to work on any one of them.
- Tyrant505 15y ago
  I really like your p#3. My additional note applies just to me learning ruby and rails and would hope to take your code further as I progress. I guess what my concern: 5K is fair of course for your level of expertise, but I would love to have it for me to build on and learn on. A bit nieve to hope it would make it into production of course, but additional building and small changes in ui(I know better), model/db changes, logic, from the stack I've been learning will aid in me making a better "prototype", and learning! Perhaps after the initial 2 week job, additional tweeks on hourly or second iteration could be in order?

ibdknox 15y ago

I actually think the timeframe works out perfectly. With two weeks you can have something complete enough to watch people use (or not) what you intend to build a business out of. At the end of the day, it's hard to learn much until you see people use it. A great deal of my time at Microsoft was spent proving that our users didn't do things the way we thought they did. We never could've done that until we had something real. The intent is for this prototype to generate the exact "added ideas" you suggest. Two weeks doesn't seem long enough that the whole world is likely to change out from under you... especially if you have nothing to show people.