Live data from Hacker News

My Y Combinator experience

marcobambini.com

111–120 of 152 posts

Re: My Y Combinator experience

#111
post #75

My guess is: You're just too early for YC. They have so many applications where the business/growth side of things are farther along than in your case, and they'd rather pick those companies for the finite amount of spots that they have at this time. They wouldn't say they were impressed by your product unless they really truly were. They're just waiting for some more validation because they have had companies try to…

I am one of the YC lawyers who was in the interview room and I was actually pretty pumped to hear the description of 20 year olds (I'm in my 40's)...

I also take exception to the comment "Y Combinator has been created for one single purpose: to make money." That's a pretty cynical view, but more important: it's not true at all.

Re: My Y Combinator experience

#112

Earlier quoted context omitted.

You seem to think that fast product iteration and testing with customers is the only way to go. It isn’t. The most ambitious projects sometimes need bold commitment. For instance if you want to create a space travel company, you will need funding way before you've finished your proof of concept. Now, maybe Y Combinator is simply not their market.

Exactly. Applying to YC was a mistake: it's an accelerator for making money, not an incubator for innovation.

Are there such things as incubators for innovation? Example?

Re: My Y Combinator experience

#113

Earlier quoted context omitted.

Things like "(Eclipse Holy God, you really just said Eclipse??)" really come across as pretty negative to me and I'm no big fan of Eclipse. All the questions asked seemed pretty reasonable to me - after all the person asking the questions is looking at it from a business rather than a technical perspective. If someone who is running a company can't adapt to the type of person asking the question then I would see that…

I actually would of reacted the exact same way. It's clear that this is a completely new dev environment and an intentional divorce from xcode/eclipse etc. The people interviewing couldn't get that. They showed zero understanding of the problem space. They were clearly stupid.

>The people interviewing couldn't get that. They showed zero understanding of the problem space. They were clearly stupid.

It's always possible that they wanted to see how the team would react to those types of questions. We had a very similar experience during our interview (asked questions that we thought were clearly explained in the application).

There was a bit of discussion on this topic yesterday here: https://news.ycombinator.com/item?id=9147252

Re: My Y Combinator experience

#114

Earlier quoted context omitted.

> i don't know where this meme that we will only fund companies with traction came from, but it's not true. Regardless of the selection criteria, would you say that as the batches have gotten larger, there is more of an advantage to having traction going into demo day? I can't help but feel like, at least for a consumer web startup, if you're just launching your product 4 - 6 weeks before demo day then you're probabl…

I don't think that's true. I think even on-the-napkin stage ideas also can use a lot of YC input to drive development in right direction. I believe it is important to at least have a prototype at least a few weeks before demo day in these programs, but that depends, of course. I think you're looking at companies that would fail without sucking in every last bit of YC juice. Those kind of companies will fail anyway.

> Those kind of companies will fail anyway.

Given the same company before and after launch, it's hard to see why waiting until you have traction before doing YC would decrease your chances of being successful. At best you get a lot of interest on demo day and save a month you would have otherwise spent raising money, and at worst you're not really any worse off than before. (This is assuming you can figure out how to make a good product on your own, and that not doing YC earlier won't slow you down at all. Not true for all startups.)

There's no question that earlier companies still get a ton of value out of YC and that it's still worth doing even pre-traction, but that wasn't really my question.

Re: My Y Combinator experience

#115

Earlier quoted context omitted.

Yes. YC will not fund the company that will invent something new. They will fund a company that looks like it might be a good business and make money. These two things aren't inherently incompatible in theory. But we've seen time and time again in practice that they are. To invent new things you need Xerox Parc (the PC) or a big government program (the Internet). To make a lot of money off the inventions, you need Ap…

I don't think that's true... YC funds plenty of inventive companies (sometimes based on idea alone). Still, the onus is on the founders to articulate why they're the ones to pull it off and how their inventions could plausibly become billion dollar companies.

Can you name an example?

Re: My Y Combinator experience

#116
post #105

Earlier quoted context omitted.

Exactly. Applying to YC was a mistake: it's an accelerator for making money, not an incubator for innovation.

If you don't think consumer software like Dropbox or marketplaces like Airbnb are innovations, consider that we have funded companies like Gingko Bioworks (synthetic biology) and Helion Energy (nuclear fusion). One thing you're right about: we're not an incubator. http://techcrunch.com/2014/07/16/why-the-first-yc-backed-bio... http://techcrunch.com/2014/08/14/y-combinator-and-mithril-in...

YC is not really for technical innovation, it's for product development: it's for taking X and doing something new with it, not for creating a revolutionary new X. For example, you certainly might have funded Facebook but I don't think you would have funded Google with Page Rank. There were a lot of search engines at the time and there was no clear market for it.

And that's not pejorative -- there's nothing wrong with that; you're not crying yourself to sleep at night.

Your whole application process reflects it: with tiny textboxes and the 10-minute interview time frame. It's perfect for saying "We're like MySpace for college students," but not at all appropriate for saying, "We use a new form of compiling search results that place ranking based on complex algorithm of reputation-based weighting."

A funny example was given by Noam Chomsky. A producer at CNN (IIRC) once told him they wouldn't feature him because "he is from Neptune and lacks concision." To which he replied something like that it was fair, because if you're saying something strikingly different, you look like you're from a different planet, and then you need to justify how you got there, and that means you have to talk a lot, so by definition you lack concision.

If these guys have spent years writing their own VM, they need a lot of time to talk about why they did that, the corner they turned and all of the complex differences their VM exhibits. A one-page application is fine if you're building Facebook for Cats but if you're doing something 'from Neptune', you can't have concision. They simply don't go together.

Re: My Y Combinator experience

#117
post #112

Earlier quoted context omitted.

Exactly. Applying to YC was a mistake: it's an accelerator for making money, not an incubator for innovation.

Are there such things as incubators for innovation? Example?

Yeah. In Europe there are incubators that are based, not on market demand but on technical innovation, and offer public money; no equity is taken.

Re: My Y Combinator experience

#118

Earlier quoted context omitted.

I don't think that's true... YC funds plenty of inventive companies (sometimes based on idea alone). Still, the onus is on the founders to articulate why they're the ones to pull it off and how their inventions could plausibly become billion dollar companies.

Can you name an example?

Two hard-technology businesses YC has funded are Helion Energy and UPower.

Re: My Y Combinator experience

#119

Earlier quoted context omitted.

But some products can't be validated in their early stages. It's hard enough to find early adopters willing to spend hours learning a new IDE and language that no one else uses. If the product is also buggy or missing important features, who would want to use it? It's also not a brand new paradigm they're inventing. Look at Game Maker which is pretty commercially successful.

So if they don't validate their product, are the Creo folks building the product for the love of it?

It's a calculated risk. If no one risked building such products we wouldn't have innovative operating systems, languages, storage engines, etc.

Re: My Y Combinator experience

#120

I'm also reading some cultural clash between American and Europeans/Mediterranean mentalities. Prioritizing your business model over your product and answering amiably to annoying questions are decidedly "American" behaviors. That's not to say these aren't great practices for aspiring entrepreneurs. When you're ready to apply again, maybe you should consider hiring an Italian guy with an American MBA who can bridge t…

Totally wrong. The technical bias shown here is every bit as strong in American entrepreneurs who lack experience pitching a product. I see this still all the time and it took a few of these painful holding up a mirror experiences for me to start seeing things from multiple perspectives. If they have the courage to really examine what went wrong here they will come back much stronger.

You're definitely right about the technical bias. Most comments here support this theory. I just offered a supplemental explanation, based on my experience.

Kudos to you for overcoming that bias. I'm still working on it.

Post reply on HN