3 ms·

After a few months I had a prototype and it actually worked. The application screen-scraped data, stored it in a database, presented it to the user, and then su

• irahul 15y ago
  Not sure if you are being sarcastic, so I am taking it as you were serious. There are arguments both for and against taking a few months to do it yourself when someone could have done it in day. He invested his few months and now he has the credibility and experience to implement the prototype himself, talk to technical founders, manage contractors and see through bullshit. On the other hand, if this was all his prototype was, he could have paid someone hourly rate to build it and then launched early and improvised. He could still have learned on his own time - he would have saved a lot of it by trading it for some money.
  • billforsternz 15y ago
    Pretty sure he was being sarcastic actually.
  • jleader 15y ago
    It also depends whether that "few months" was solely spent learning the technology, or whether it was also spent iterating on the concept. It could be that if he'd hired someone, he'd get a prototype of his initial concept in a day, but then have a harder time iterating because he didn't really understand how the prototype worked.
  • Shorel 15y ago
    He paid with his own time, for something much better than simply the software: He is no longer in the path of becoming a PHB.