3 ms·
The way Ray Dalio describes it in "Principles" is very helpful in my opinion. He says whenever you are trying to solve a problem, rather than just doing it you
by seanhunter 4y ago
The way Ray Dalio describes it in "Principles" is very helpful in my opinion. He says whenever you are trying to solve a problem, rather than just doing it you should imagine you are trying to build a machine to do it. And if you are trying to perform a task you should imagine you are writing the script for a movie in which the task is performed.
The advantage of this second-order thinking is then you have a different frame of reference. You can for example compare the actual outcome to the script of the movie you imagined before. You also have more obvious agency and different choices. When you are designing your machine you are making concious choices and evaluating your options more specifically than if you are just plowing ahead with the obvious route. The machine analogy also means you can focus more on how you make the task automated, sustainable etc. So for example in tech rather than just doing a job, you write a script so next time the job becomes trivial, or (better) you automate the processes so you don't need to do the job again.
- Shugarl 4y agoOoh, interesting. Up until now, I'd just imagine myself solving the problem manually, then describe that with code. I'll try to imagine building a machine to see how it feels
- l33t2328 4y agoFor me, building a machine is identical to writing code. I can’t really see a difference.
- seanhunter 4y agoI personally don’t see a difference either. Dalio isn’t a programmer - he’s an asset manager who just tries to think in a systematic way. One of the reasons I like this analogy is that it resonates with me as a programmer.