-
-
Notifications
You must be signed in to change notification settings - Fork 3
/
root-thinking.scroll
37 lines (25 loc) · 2.13 KB
/
root-thinking.scroll
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
date 11/16/2022
openGraphImage rootThinking.png
tags All Programming Thinking Scroll
title Root Thinking
header.scroll
printTitle
thinColumns 1
I dislike the term _first principles thinking_. It's vaguer than it needs to be. I present an alternate term: *root thinking*. It is shorter, more accurate, and contains a visual:
dateline
rootThinking.svg
caption Sometimes we get something wrong near the root which limits our late stage growth. To reach new heights, we have to backtrack and build up from a different point.
endSnippet
All formal systems can be represented as trees^tn. First Principles are simply the nodes at the root.
https://en.wikipedia.org/wiki/First_principle First Principles
## Root thinking becomes more valuable as current growth slows
Technology grows very fast along its trendy branches. But eventually growth slows: there are always ceilings to the current path. As growth begins to slow, the ROI becomes higher for looking back for a path not taken, closer to the root, that could allow humans to reach new heights.
## Root thinking isn't as valuable when growth is rapid
If everyone practiced _root thinking_ all the time we would get nowhere. It's hard to know the limits to a current path without going down it. Perhaps we only need 1 in 100, perhaps even fewer, to research and reflect on the current path and see if we have some better choices. I haven't invested much thought yet to what the ideal ratio is, if there is even one.
****
## Notes
^tn Tree Notation is one minimal system for representing all structures as trees.
https://treenotation.org Tree Notation
# Update: 7/1/2023
On second thought, I think this idea is bad. The representation of your principles-axioms-agents-types-etc rounds to irrelevant. Infinitely better to spend time making sure you have the correct collection of first principles than worrying about representing them as a "tree" so you can have a visual. It's knowing what the principles are and how they interact that matters most, not some striving for the ideal representation syntax. This post presents a bad idea, but I'll leave it up as a reminder that sometimes I'm dead wrong.
footer.scroll