Database connection error... Cached: http://webcache.googleusercontent.com/search?ix=acb&sour...
Thanks for the link, didn't expect to see an error
Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
21–30 of 160 posts
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#22Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#23You know what works better?
Build something nice and polished (anything) and show them that.
Big claims work better when you're not coming empty handed.
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#24Being able to ship a proof of concept (a precursor to an MVP) is a pretty core skill that will happen many times in that thousands of hours.
Other fun questions in the perpetual proof of concept game:
Will it work this way? Will it work that way?
I don't know. How long will it take? Can we quickly try it out somehow to see if it gets us what we need? Who can jump on this?
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#25[deleted]
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#26I don't think that YC is trying to identify teams that can create the maximum amount of value in 72 hours. They're looking for teams that will create the maximum amount of value over thousands of hours (or more). It's not at all clear that the former correlates with the latter.
I think you're correct a long-term push is different from a 72 hour scramble but they're only looking to "win" an interview, not a place in a starting class. I think it's reasonable a team could be unsuccessful at filling out an application (which previously required an idea) but still be extremely strong candidates. I hope YC accepts, they don't stand to lose anything (save time) and there's no obligation to accept…
Ya, I'd tend to think it's at least worth pg sending them a challenge.
That being said, I don't think that what successful YC applicants are doing should be characterized as "filling out an application." The application just captures their past work in a form. It's the actual past work that matters, not the simple transcription.
I think my larger point is that an awesome 72 hour hack session probably isn't as good of an indicator of future success as a track record of successful medium to long term work in the past.
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#27You guys should post about your startup here while you have some attention. Sounds interesting (I am assuming you are applying with the seed launcher idea?).
Without being an expert in startup financing I'd imagine there would be some fairly significant regulation challenges in the idea? Anyone successfully using the platform currently?
It is also interesting that your idea itself if it comes off might be solving a YC problem (How best to connect pitching startups with the right investors and generate the best valuations).
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#28Earlier quoted context omitted.
True that, build something amazing in 72 hours. You are not just idea implementation and realization machines.
We'd be in for that too. We have tons of ideas waiting on deck so to speak.
Then go and build one of them in 72 hours, live blog it, and post it here. If it's interesting, surely it'll get upvoted, and then at least some of the YC partners will take notice.
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#29> This is the second time we’ve applied to Y Combinator. Our dream has been, for a while, to get our startup off the ground
I don't mean to be crass, but
1) This seems to imply that doing Y Combinator entails success, which is backwards.
2) What has the startup been doing since when it was last rejected? Why try to showcase a random thing you can do in 72 hours instead of showcase how you can build your startup in the months in between YC sessions?
Re: Dear Y Combinator, we bet you we can solve a problem of yours in 72 hours.
#30hey guys getting database error on your blogs.