I guess you could do 1 minute conversations and get it down to about 8 hours, although even assuming you can get 500 people to queue up for this, I'm curious what will come out of 500 x 1 min. back to back conversations.
It seems to me that the only useful way to get feedback from 500 people in one day involves sending out some kind of survey. Then again this isn't really my area of expertise, so I'm curious, how would you go about gathering feedback from 500 people in one day?
Not saying I am in full agreement, but it's pretty clearly the purpose of the parent comment.
Programmers aren't immune from overestimating their competency, and if you are about to get into a venture with someone you don't know well, I think it makes sense for both sides to do some due diligence.
I would actually phrase it differently: programmers quite often overestimate their competency. I am not sure if it is unique to programmers or just an instance of the general inability to objectively analyze ourselves, but I do notice that the vast majority of programmers I have met (myself included :)) have a tendency to consider ourselves a smidge more capable than we actually may be from a purely objective standpoint. Then again the stretching is what grows great developers, so that overestimation that spurs you into attempting things just outside your current grasp is probably a net positive.
Satire aside, it's enough to make me wonder if talking to 500 people is as trivial as setting up a twitter account. Setting up a twitter account or a C Corp is really not that hard to do.
Only way I can think of is to do a survey and enlist the help of bored college students to stand in front of of a busy intersection. I'm guessing part of the "soft skill" is recognizing that > 90% of the people walking by won't even be interested in stopping and talking. (Or send an email/twitter/whatever blast somewhere. Or something). But essentially, "talking to 500 people" is not necessarily "talking one-on-one".
I think that says a lot more about the difference in mindset between the geek and the suit than anything else.
A geek does not typically approach an outsider and say 'I've got skills can you come up with an idea for me?'. But on the flip side 'you have skills, I've got this idea' is a -very- common occurrence. If you are the one doing the approaching applying your own quality control is a given.
If against the odds you are being approached by an unknown geek wanting to partner with you, then testing their skills should be part of the process yeah, you both have to be confident in each other; though I would consider the above methods to be a truly terrible interview...
Finally, before I even consider hustling customers and investors I want some paltry measure of ability. If you can hack something together in 24-48 hours or even a week, then they're quality geek co-founder material. Any longer and it's a judgement call. Most won't get past step one, and you certainly didn't want them as a co-founder.
I have learned this the hard way. I raised money only to find out my tech co-founder couldn't push code in a timely manner. This street goes both ways and that is why teams of 2 work best, one to build it and one to sell it to the world. The question for me is, can the geek cut it?