Books Every Entrepreneur Should Read
thedailymuse.com
thedailymuse.com
- Scriptures of the major religions
- The Conquest of Happiness (Bertrand Russell)
- On Aggression (Konrad Lorenz)
- Crowds and Power (Elias Canetti)
- LSD, My Problem Child (Albert Hofmann)
- Huis Clos (J.P. Sartre)
- Essays by Michel de Montaigne
- The Incoherence of the Incoherence (Ibn Rushd)
-Losing my virginity (Branson)
-How to win friends and influence people (Carnegie)
-Venture deals (Feld)
-Man's Search for meaning (Frankl)
On a business side I personally like, "Postively Outrageous Service" & "The Heart of Change"
- Makers (Cory Doctorow) -- I recommend this to every entrepreneur and technologist I know, if only because it will inspire you to create something great.
- Masters of Doom (David Kushner) -- History of id software
- Game Over (David Sheff) -- History of Nintendo; seriously wild
http://en.wikipedia.org/wiki/Homo_ludens
http://en.wikipedia.org/wiki/Cryptonomicon
Just my 2 cents on the list that actually matters.
Decision Points - George W. Bush
http://www.amazon.com/Decision-Points-George-W-Bush/dp/03075...
Fooled by Randomness: The Hidden Role of Chance in the Markets and in Life, Nassim Nicholas Taleb
I don't know if I've read it somewhere and I'm regurgitating it or if it's my own original thought, but I'm going to call this the Malcolm Gladwell effect. Take your limited scope, strip away the "irrelevant" pieces (regardless of how much they could've actually mattered), package up a bunch of anecdotes that convey the point you want them to, and make people feel good about that part of themselves.
Complete bunkum.
Sorry for the excessive use of quotations, I just wanted to emphasize the bullshit.
If you can name-drop the latest fad, then the elite ninja hacker coder you're trying to hire will think you're part of their clique and speak their code - they will consider you an ideological comrade, and they are much more likely to come on board without thinking too much about working conditions or how the company is about to fail! Then you can get them on board and focus on your top priority: making sure you cash out before it does.
Dollar-for-dollar, a 1993 book like "Code Complete" just can't compete with that kind of usefulness. /s
The more books an entrepreneur reads, the more he/she may realize, that the success of the enterprise is more or less random (if you don't believe that, read Daniel Kahnemann: thinking fast and slow - but that advice would be against the advice I give in this post ;O). Its much better not to know all the problems in advance and get scared away. Instead, just start and solve problems as they appear. Stay motivated, hold alive a positive attitude and remain in good mood contributes most to success IMHO.
And while youre still reading, someone else may start your business...
But who am I to give advice to entrepreneurs? I'm not an entrepreneur myself (read too much).
Yeah, you're probably in over your head. But you won't know till you try, and being in over your head and knowing it's all up to you is a pretty fantastic motivating power to overcome that difficulty.
I always cringe when I see lists like these. These books aren't even interesting! Pretty much everything you need to know about becoming an entrepreneur can be found on PG's site, and the rest can easily be found by searching the web. There is no hidden secret to working hard and solving problems.
I'd much rather spend all the time I'd be reading these books by reading something interesting and useful, say, a book on macroeconomics (you can of course pick a different subject if you don't like thise one) or even fiction (at least that's fun).
If you want to be good with UX you don't read books about UX you read books about psychology, typography, color-theory, comics.
If you want to be a good entrepreneur you read about well everything kitsune_ wrote and even non-fiction.
You can't read your way to experience.
This reminds of a decision making book which are based on empirical observation and theory. Good if you want to know how to make decisions in ambiguity, uncertainty and other complex situations.
Streetlights and Shadows: Searching for the Keys to Adaptive Decision Making - Gary Klein
http://www.amazon.com/Streetlights-Shadows-Searching-Adaptiv...
This list looks like it was written by somebody who reads pop-business books, and doesn't run a business.
Alternative : Try Venture capitalist at work by Tarang Shah
http://www.amazon.com/Venture-Capitalists-Work-Billion-Dolla...
- Startups fail because they run out of money
- VC's like to invest in smart passionate entrepreneurs who are solving a personal problem who are not in it for the money.
- VC's like either big markets or great teams or both
- etc etc
Some of the interviews were great (Howard Morgan) but the problem with interviewing active vcs is that they can't talk about the stuff behind the scenes. Often founder's who have had successful exits have no such qualms.
http://www.amazon.com/The-Startup-Owners-Manual-Step-By-Step...
I occasionally look through the business books section of a bookshop while waiting for my train home from work, and I'm always struck by the intellectual emptiness and embarrassing obsession with the latest fad of most of these books. I wonder how this sector of the book market got like this?
The Art of the Start
The Innovator's Dilemma
The Four Steps to the Epiphany
Positioning
The 22 Immutable Laws of Marketing
The Lean Startup
Blue Ocean Strategy
Business Model Generation
The Fountainhead
Atlas Shrugged
among others...
I would personally throw in an autobiography a functional business book. The rest can be made up with personal drive and passion.
http://www.catchcamera.com/2010/07/13/the-16-best-business-b...
Stuff that counters the "worked once for me" quality of so many how-to business books.
Only reading success stories is horribly misleading.
The only thing I read are (auto)biographies of successful entrepreneurs or books written by successful CEO's.
I don't need to know insights of some theoretics - they usually don't know shit.
Would you read a book about JAVA written by someone who never wrote a 1 line of code? Only looked what others did?