But first this has inspired me to get to work on the forgotten Part II.
Can you please provide a glimpse of what you want to address in the re-write.
There's generally less great content on the idea/0 to 1 compared to the 1 to n stage imho. I've found work from Michael Seibel, Des Traynor, Mathilde Collin, Brian Balfour and others to have been very helpful for the super early product design thinking stage in addition to the playbook.
We already tried this in the larger tech community. At best the controversial or contrarian views were silenced, at worst, people’s lives were ruined.
It should be in Google Play & iTunes shortly
Either iterate through each section guessing the URL or give dev tools a go.
EDIT: See my comment here for all of the mp3s: https://news.ycombinator.com/item?id=18917784
>So I'm not suggesting you be good in the usual sanctimonious way. I'm suggesting it because it works. It will work not just as a statement of "values," but as a guide to strategy, and even a design spec for software. Don't just not be evil. Be good.
As a founder I think the Playbook is mostly on point, I'm curious to see what Sam adds or removes in the re-write. Startups are hard and it takes a lot of persistence and hustle to move the needle in a meaningful way. I love the part in the Intro section "A word of warning about choosing to start a startup: It sucks! One of the most consistent pieces of feedback we get from YC founders is it’s harder than they could have ever imagined, because they didn’t have a framework for the sort of work and intensity a startup entails." Then the follow up line is great "On the other hand, starting a startup is not in fact very risky to your career—if you’re really good at technology, there will be job opportunities if you fail. I personally think the riskier option is having an idea or project you’re really passionate about and working at a safe, easy, unfulfilling job instead." - I totally agree with that, if you have an entrepreneurial character you'll forever regret not taking the chance.
Either iterate through each section guessing the URL or give dev tools a go.
EDIT: See my comment here for all of the mp3s: https://news.ycombinator.com/item?id=18917784
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
https://storytime.voxsnap.com/30/audio/2018/09/14/ycombinato...
2. Many times I shared the Playbook, people failed to consume it.
3. Based on (1+2) idea: to make a short overview of the Playbook. Like those 3-minute hand-drawing YouTube videos. @sama could narrate one and make it as widespread as “Here’s to the crazy ones...” mp3 we all might have, narrated by Steve Jobs.
"Literally watch them use your product. Sit in their office if you can. Value both what they tell you and what they actually do. "
^^ If anyone is having a hard time with any of the above, let me know. Happy to offer a free user video on us. We work on an on-demand/automated remote user testing service to help you learn from your users much more easily and quickly:
The bottom line of a CEO is to make the company successful and to make decisions with conflicting advice but this provides the bit that the best CEOs cannot always know and that is only from experience so I love the ballpark numbers, the common mistakes and the counter-intuitive advice.