Talking one-on-one to 500 customers in one day to get feedback doesn't seem possible. If you only spend 5 minutes talking to each customer, and you have them lined up back to back so you don't waste time in between, it would still take 40+ hours.
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?
The entire post was a satirical response to the GP comment. It was meant to show how, depending on your point of view, the same logic can be applied to either the tech or the business side and maybe even "look good" but seem unreasonable to those on the other side of the table.
Not saying I am in full agreement, but it's pretty clearly the purpose of the parent comment.
I had a feeling that might be the case when I started reading about the 500 people in one day bit. The second half however, about assessing whether the future technical co-founder can actually build a prototype over a weekend, seems like reasonable advice.
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.
>Programmers aren't immune from overestimating their competency
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.
The reason is because the skill appears as magic to others, whereas business skills are something that anyone can at least imagine themselves doing. This is completely orthogonal from how difficult these jobs may be under varying circumstances.
Except that it is possible to hack together something in 24 - 48 hours, or a week, assuming you are willing to pare it down to essentials and fake parts of the demo.
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.
I am curious about that too. I'm taking it at face value that "talking to 500 people" is as trivial as setting up a twitter account.
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.
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?