729 karma · joined October 20, 2012
It is likely that you misunderstood PG. He is merely saying that even with all the work, you won't always be right in picking an idea. However, this does not imply that you should put no work on it and start acting on blind faith. In fact I am pretty sure YC does not fund teams who haven't spent at least some time analyzing their idea.
Blind faith is a bad idea. You want to start with an idea and become its biggest enemy for a few weeks. You need to attack it from all angles, talk to potential customers and try to find reasons why it would not work and why you wouldn't want to spend the next 5-10 years of your life building it. If after several weeks you still cannot prove that you have a bad idea then congratulations you have a good idea candidate.
Luck is still going to play a big role in your success but at-least you have a sound starting point.
I will have an answer for you in a month because I am going to start trying this strategy out in my current job starting this week. :)
It feels we need to do a better job quantifying this problem before we come up with a solution. For example (1) how much money would it take to fix health care? (2) how much money would it take to fix welfare? (3) what is the impact of low savings rate on people's economic condition. For example appearance of credit cards coincides with the timeline in this article (4) How has immigration impacted unskilled workers? (5) Does UBI work? (6) How is Europe doing it? (7) Is Europe really as successful at dealing with these issues as everyone seems to claim?
In short, RSS is a feed of (mostly) professionally written articles while Twitter is full of amateurs expressing half baked thoughts in 140 characters. It is unfair to compare the two.
Atleast in my life, shorter work hours tend to heavily inversely correlate with my work output.
I wonder how (1) the software has evolved to face this new reality, (2) how much of the old code is still being used and (3) what are the performance penalties we pay for using disk performance characteristic assumptions in code that actually runs on solid state drives?
Next gen. communication tools like fb messenger, WhatsApp etc. solved this problem by making the default expectation asynchronous. It was a huge step in evolution of messaging.