Tyler Cowen on reading fast, reading well, and reading widely
- Be ruthless with the books that are not good. Just stop reading, put them down, usually throw them away, don’t give them away – if you give them away, you could be harming people.
- The way you read well is just by reading a lot, and by reading a lot your whole life.
- The best reading is focused when trying to solve a problem.
- Reading fiction is important to understand the cross-sectional variation in humanity, to understand how difficult generalisations can be, just to get a sense of how different social pieces fit together, and to get a sense of different historical eras – and plus, reading fiction is often just plain flat-out fun.
- In every area you don’t give a damn about, you probably should read at least one book. Because the best book in that area is superb, you’re not going to know what it is.
- People don’t read enough, and I think as a society we’re under-investing in reading. People feel compelled to finish books they’ve started – that’s just a tax on your reading. Why would you do that to yourself? Imagine a world where any restaurant you tried, you had to keep going there for days or weeks, you’d hardly ever go out to eat.
- Take reading seriously, develop a passion for it, and view it as part of your practice as a knowledge worker to get ahead, but along the way, have fun doing so.
- Strive for a great UX and a good-enough UI
- Talk to users (even if you don’t think you need to)
- Start building a growth engine before you need it
- Expand scope in good times, narrow it in the bad
- Focus on skills, not functions
- Be a power user of your own product
- Overcommunicate, don’t overpromise
To innovate, exploit unrecognised simplicities.
There isn’t one novel thought in all of how Berkshire is run. It’s all about what [Mr. Munger’s friend] Peter [Kaufman] calls ‘exploiting unrecognized simplicities.’ We [Messrs. Buffett and Munger, their shareholders and the companies they have acquired] have selected one another. It’s a community of like-minded people, and that makes most decisions into no-brainers. Warren and I aren’t prodigies. We can’t play chess blindfolded or be concert pianists. But the results are prodigious, because we have a temperamental advantage that more than compensates for a lack of IQ points.
- Rather than asking someone what they do, ask them what they’re excited about right now. It leads to a 10x better conversation.
- Instead of studying how Bezos made his billions, it’s much more useful to learn how someone like you makes $10K/mo. So often, we try to gain lessons from the outliers when in reality, we can learn from our neighbours.
Some ways to get better at debugging
- Learn about the codebase, system, tools and strategies to get better at debugging
- Debugging is the best way to learn how a new codebase works – seeing how something breaks helps you learn a lot about how it works.
- To fix bugs, you often need to learn much more about the broader environment than the language. You need to learn about the domain.
- Learning about your tools will make a huge difference.