Paul Graham, it’s time to put your money where your mouth is
blog.helioid.com
blog.helioid.com
"Don't try to construct the future like a building, because your current blueprint is almost certainly mistaken."
Let me conclude with some tactical advice. If you want to take on a problem as big as the ones I've discussed, don't make a direct frontal attack on it. Don't say, for example, that you're going to replace email. If you do that you raise too many expectations. Your employees and investors will constantly be asking "are we there yet?" and you'll have an army of haters waiting to see you fail. Just say you're building todo-list software. That sounds harmless. People can notice you've replaced email when it's a fait accompli.
It was in the 'tactics' section near the bottom of http://www.paulgraham.com/ambitious.html
That's what I said. I just quoted a different part of the same section :)
Just based on counting noses it's clear that there's a bunch of YC companies every year which vanish without a trace; I'm sure many of them were failed runs at frighteningly ambitious ideas.
Maybe a 6 month version of YC where more money is invested could work, but I don't think YC is setup to support those types of ideas. I'm sure someone out there can surprise me though...
I think that as a startup, pointing your bat to the stands is something best left for investor meetings and internal goal-setting. In the press, it might not go over so well.
Search: Greplin
Email: eTacts (sort of), Taskforce (emails => todo list), Xobni
Movies / Music: Earbits
Publishing: Hyperink
These are just off the top of my head. I'm sure there are more. Does the author want an entire class to be new search engines?
Search: Hipmunk, Octopart
Email: Streak
Movies/ Music: Can't Wait, Like.fm, Teevox, Nowbox
* justin.tv pioneered live broadcasting online
Dear startups,
If you want to do something very innovative, don't apply to YC with it. YC is a three month program designed to make companies; it is not a research program. On the application, you will have to describe what you're working on in three sentences. That's not a design flaw; they're looking for things that can be described in a few sentences.
There have been exceptions -- people that went through the program who were (and are) working on hard problems -- but if you look at the numbers, they are clearly the exception.
YC is great. I'm glad it exists. But understand what it is, not what you want it to be.
I took that essay as a call for more people to please start applying to YC with really big ideas so they can fund more of them.
Though I guess they could convince people to drop a good idea for a pie-in-the-sky idea, but I think what happens more often is that they get them to drop a mediocre idea for a better one.
But anyway, YC gets like 2k apps per cycle, but most of those are going to be for non-devastatingly-ambitious ideas, and then the ones that are have to have great teams behind them. If you don't see very many coming out of YC, it might be because there weren't that many to start with.
> that the biggest opportunities for revolution often sound like the craziest ideas at first. Graham points out the flawed reasoning in investors’ so often shying away from projects trying to pull off these sorts of major revolutions, but Y Combinator itself mostly gravitates toward startups making relatively small, iterative progress on existing idea spaces
Graham is pointing out how frightening these startup ideas are because they are existing markets ripe for some innovation. Eg. search, universities, compilers.
Edit: Also, compilers to move code from mainframes to commodity servers, recompilers to switch architectures (e.g. Rosetta by Transitive), etc are big business. Are they going to make you a billionaire? Probably not. Can you make a couple million and a great ROI? Absolutely.
I speak with some fair knowledge of compilers, PLs, runtime systems, and OSs when I say: massive companies will also throw money at me if I can turn lead into gold.
A compiler cannot transform an inherently stateful, sequential program into an inherently parallel program that can be easily parallelized-the-hell-out-of. This is why there has been actual interest in shifting over to functional programming among those who need lots and lots of concurrency.
There do exist systems that will, for example, guarantee the determinism of threaded applications -- making them more predictable and debuggable. But DThreads still won't take a fold and turn it into a map.
Given enough time and memory more things are possible. Heck you could probably add speculative execution to many programs for more speedup. You are right in that the easy stuff has already been done, but that doesn't mean the hard stuff can't be done - just that it is hard. The good news is that people are prepared to pay for hard stuff.
2) You've gone into the research world, which concedes my original point about it not being a viable business ;-).
2) Not really. You've used current thinking to define your business model. Think disruptive instead. And worst case you'd end up spending Ycombinator money and end up with a better CV.
Some thoughts: It is possible now for a compiler to chew through terabytes of open source code to build up an information bank. Internal representation of code can be centrally submitted to see if anything matches and provides more compilation hints. Runtime profiling could submit back big O information. An organisation could run all the possibilities Seti-at-home style. ie rather than the compiler having to make more intelligent choices, it can just try all the choices.
To my knowledge, the middle step is actually the hardest. I'm no statistician, but do we have math/software that can look at a curve and distinguish a logarithmic function with little error in the data from a linear function with lots of error in the data?
>2) Not really. You've used current thinking to define your business model. Think disruptive instead. And worst case you'd end up spending Ycombinator money and end up with a better CV.
The man-years here are the dominant cost. A SSC falls outside the start-up business model of releasing a "Minimum Viable Product" and all that jazz. You can't build a minimum SSC without building most of the whole thing.
That doesn't mean I wouldn't take someone's money to do it, but I'd be asking for a research-project budget, not an equity investment that has to be "ramen profitable".
Besides, I prefer home-made vegetable curry to ramen any day ;-).
You are still thinking "cathedral" as the project structure. I think "bazaar" is a better approach - try all the things, fling stuff against the wall and see what sticks. Use the terabytes of existing code to learn. I see the latter like spoken language translation. The approach used to be coming up with rules from experts which is very expensive. Nowadays they use statistical approaches which relies on having lots of data, uses humungous amounts of machine time to build the translation, but uses very few (expensive) people.
A YC startup doesn't have to be profitable or even come up with a MVP - it has to show there is merit to what they doing and some probability of success in the long run.
This means not having to guess big O correctly, or access patterns or other stuff in advance. It is possible to add future optimisations and not worry about current ones since they just won't be used work inapplicable workloads.
Then what's the point of a YC startup? Doesn't have to make a profit, doesn't have to build a product... basically, sounds like it doesn't have to build a company.
what I'm getting annoyed at is the tone I'm sensing -- it's sometimes downright sneering. i know it's been brought up very recently as well, and PG has said it's been happening gradually as the site has grown. i've read the essay on trolls, but this seems like it's something different. jealousy is also something that increases as a function of success, and when jealousy crosses a threshold, it morphs into resentment. just sayin'...
Whenever a lot of people start getting really excited by someone or something, I think that there is a certain subset of people, myself included, that react by getting overly skeptical, by looking for the problems. Personally, I try to be thoughtful and present any negatives I find in a polite and well reasoned manner, but I am sure that there are others who simply have a knee-jerk reaction of the sort: "I can't believe you're drinking the Kool-Aid, you idiot."
There is far too much focus on selection bias around ideas in both this article and the comments, when in fact PG is simply putting faith in teams that happen to be passionate about certain ideas (that may or may not fall into his ambitious ideas categories).
I remember somewhere that AirBnB said they wanted to become the best marketplace for trading used goods. That's pretty ambitious, but they're attacking it sideways by letting people rent out rooms first.
Or a least a byline.
It's a deceptively focused/small offering to start with but they have the key components required to become a credentialing system outside of the university/college system.
It's easy to look at YC startups and say they aren't pursuing massive visions but the truth is many of them are just starting with some tiny subset of a big problem.