(The English version follows)
今天的分享来自 Neil Kakkar，我们之前的 Daily Productive Sharing 056 - 20201103 就是他介绍如何利用复利理论来对待点子。他在这篇里分享了自己过去十年学到的一些技能：
如果你想更好地管理时间，并且减轻自己的压力，不妨试试 BRNR List
如果你也想成为更高效的人，欢迎加入我们的 TG group
如果大家使用邮件订阅，请把 email@example.com 添加为邮箱联系人，避免邮箱过滤的误伤，谢谢:)
Today's share comes from Neil Kakkar, whose previous Daily Productive Sharing 056 - 20201103 was an introduction to how to use the theory of compound interest to approach ideas. In this post, he shares some of the skills he has learned over the past decade.
- Learn to take compounding seriously
- Learn to develop taste
- Learn to sequence things well
- Learn to see what others see
- Learn to make and execute decisions quickly
- Learn to spot a convex or concave world
- Learn to tell stories
- Learn to dive into the source code when documentation isn’t enough
- Learn to be specific
- Learn to see systems
Some of these skills have already been covered in our previous shares, such as compound interest theory in Daily Productive Sharing 110 - 20210115, Daily Productive Sharing 124 - 20210204, and systems theory in Weekly Book Club 006 - 20201121.
If you find today's sharing helpful, why not share it with your friends?
Try our sustainable productivity tool BRNR List
So, learn the most basic, most useful skills first. The longer you wait to learn skills like these, the less time there is for compounding magic.
Let others tell you what you’ve made is crap. Learn why. Notice when they tell you something is great. Figure out why.
This transfers to writing as well: Popular advice to get better is to write a lot of junk, do it a 100 times, and pay particular attention to what is received well.
In effect, you bootstrap good taste by first learning what others consider good. Then, you see the system behind it. Then you break the rules and still manage to awe.
When decisions are reversible - and they mostly are - speed is a super power.
Cultivating a habit of making decisions quickly, and then executing them is better than just thinking about it.
The world is sometimes concave, and sometimes convex. Knowing your topology can help you make better decisions.
So you got to do it the hard way: read the source code and figure out what you need to make things work.
Most of the time, most people don’t know what they’re talking about. Not being specific is a sign of that. The more abstract the word, the harder it is to pin down a meaning.