Tell HN: Here's how my team got to the YC interview stage
trevorburnham.com
trevorburnham.com
- Have you fought with your co-founders yet to find out if you could survive such a fight? If all you've been in civil and polite, then you don't really know each other yet
- You have 'options'. Will you have the drive to really push through if things do not go initially as expected?
The impression I am concerned about is that you seem a bit soft and nice, if I may use those word. If I were you, I'd focus on making sure in conveying that you have the capacity to be tough also.
And yes, I do have that drive to push through. It's not every day that you get the chance to change the world. I'm not throwing that away, no matter how difficult things might seem.
As to "soft and nice"—well, thanks! I get what you're saying, but my impression is that knowledge >> toughness in the startup world. Being tough is mainly about understanding that you have other options, that you don't have to accept everything that's put in front of your nose.
Some people get to that compromise point, but some can't. If the fights are resolved in a bad manner and resentment continues to brood, when money arrives and people get greedy, those fights will come back, and this time they will be worse.
So you have to get the fights over with at the start and everyone has to accept their position and their status. Then you can work in a focused fashion forward.
Changing the world is great, but I can likely do that by planting a bunch of trees in the amazon. Very few business get to change the world - most just get to make money. Would just making a lot of money also be enough for you, even if you don't get to change the world?
It works like this: you put up the .tex source, the data files, the R, Octave, etc. scripts, and if people download and run the scripts, they get the exact paper as a result, including all the graphs. This way one can check that the graphs really show what is claimed in the paper and that there has been no bug or "polishing" of the results.
Don't forget that data can be polished as well - for a hypothetical cheater, you'd simply be moving the "messaging" work from the finished project to the source files you mention above. There's a lot more to trusting a paper then just trusting the figures; you're trusting the scientific process that a lab is undertaking, and it's almost always impractical to require proof of every stage of that process.
Another downside is that not every scientist is ok with giving access to all of their hard-earned data - that opens up analyses and potential scoops to other groups. This is especially true in biomedical/clinical studies, where data is very expensive to gather and can take years to analyze. Not saying raw data is never shared, but there is a balance there.
Finally, scientists greatly prefers testing a published claim by pursuing a follow-up hypothesis rather then redoing an existing analyses. That way you kill two birds with one stone. It's inevitable that some irreproducible results slip in with this system, but if the claims are significant enough sooner or later someone who's trying to build on the claims (and failing) will go looking for more details and the fraud is exposed. The fear of being exposed in that way is what keeps the system honest, and to a large extent this system works.
We think our most promising immediate markets are social scientists (of which there are about 25,000 in the United States) and stats/science classrooms. While the original concept was mainly aimed at researchers, we've been shifting more toward classrooms recently, based on the feedback we've been getting. The two products we envision—the research product and the educational one—share the same core, as far as the interface and computational backend. So, we believe that we can pursue both markets, much as Lingt (YC S09) has both an individual product and a classroom product.
I should emphasize that my blog post is in no way intended as a pitch for Theoryville reflecting our most up-to-date thinking about our product or our business model.