Skip to main content
Post a Comment

Zero to One - Notes...

Zero to One: Notes on Startups, or How to Build the FutureZero to One: Notes on Startups, or How to Build the Future by Peter Thiel
My rating: 4 of 5 stars

Insightful, but not really contrarian...

I have understood most of these concepts for several years, partially based on an insight provided in a beginning finance course. On the first day of class, the professor asked, "How do you make money?". The first answer was "word hard," the second answer was "provide services," but no one answered the best one, "control it." Now, one could control money, but over time I realized that it was control of a resource, essentially power, similar to monopoly, or simply an especially strong, market position.

Peter is a persuasive writer, but too often his expression of a belief is lopsided, and at least partially untrue. Yes, the companies he lauds are innovators, but later their innovation is often nothing more than market position, like buying up the entire supply chain before rivals. His example of people who believe in definite futures, as part of path to success, suffers from survivor bias; many entrepreneurs have definite concepts about the future and what they want to do, but most fail, we just don't hear about them.

I could go on, but I did enjoy the book, if for no other reason than it clarified my own thoughts about markets, and it is well-written.

As for the question, my answer would have been that inequality is the greatest threat to modern life. Although seemingly common now, since Occupy, I found the statistical negative correlations between inequality and quality of life measures back in 2003, and back then, it might have ruffled a few feathers. Also, it would be the toughest not because people do not believe it, but because the people I know and work with, as well as the people I have my closest relationships with, would see it as a personal attack. I work in finance, and some people I know and love are well-off.

View all my reviews

Comments

Post a Comment

Popular posts from this blog

Behave: The Biology of Humans at Our Best and Worst by Robert M. Sapolsky My rating: 5 of 5 stars I finished reading this crying. It is a work of neurobiology, social science, anthropology, and history, but ultimately it is a work of great humanity, suggesting ways that humans, our groups, our systems, and our societies can be made better. View all my reviews
Post a Comment
Read more

A Journey — if You Dare — Into the Minds of Silicon Valley Programmers

My responses in a NY Times comment section for the book, Coders: The Making of a New Tribe and the Remaking of the World by Clive Thompson : #1 - Link Although I've been a software developer for 15 years, and for longer alternating between a project manager, team lead, or analyst, mostly in finance, and now with a cancer center, I found it funny that you blame the people doing the coding for not seeing the harm it could cause. First, most scientific advancement has dark elements, and it is usually not the science but how it is used and sold by business people that is the problem. This leads to the second problem, in that it is not coding that is in itself problematic, but specifically how technology is harnessed to sell. It is normal and desirable to track users, to log actions, to collect telemetry, so as to monitor systems, respond to errors, and to develop new features, but that normal engineering practice has been used to surveil users for the purpose of selling. Blaming
Post a Comment
Read more

Don't learn to code. Learn to think.

A response to  Don't learn to code. Learn to think. : Below is is my usual response when I see an article stating that everyone should learn to code:  Rather than programming, it is more important to impart the thinking of computer science (CS) than a specific implementation. Programming can be an end point for some students, but it is likely that programming itself will be increasingly automated, so that one needs more the general concepts common in CS. Even then, programming itself is to some degree a grunt task that one progresses beyond:  The following are typical components of a CS degree: algorithms & flowcharting systems thinking logical systems and set theory object-orientation & patterns probability, statistics, mathematics All of the above can be useful in an increasingly automated and data-driven world.
1 comment
Read more