Conversation

This has been on my mind lately. Salvatier's blog post is great, but it's been sinking in for me that everything he says applies to major collective delusions as well. The stock market for eg. has a surprising amount of detail. So does the Marvel Cinematic Universe.
Quote Tweet
Reality has a surprising amount of detail. johnsalvatier.org/blog/2017/real But so do escaped realities. ribbonfarm.com/2015/01/16/on-
Replying to
I think the more correct, or at least more precise statement is: "reality has a surprising amount of _surprising and boring detail_" Being a reality nerd is about making that boring part interesting for yourself.
1
20
When you go down a tvtropes or fandom wiki site bunnytrail, there is an endless amount of detail to master, but it is also endlessly interesting AND not entirely surprising (like looking up the details of a minor and obscure superhero's superpowers is never truly surprising).
2
4
But if (for eg) you do what Salvatier recommends and look into the surprising amount of detail in "boiling water", it's both surprising how complex it is, and kinda boring unless you find a way to get interested in say convection physics and heat transfer in uneven metal plates.
2
7
Wong's point in that article is that effort shock is a result of miscalibrating the surprising amount of detail in reality due to the conditioning effects of karate-kid style sports montages that make it look easy, quick, and fun, with a nice soundtrack.
2
7
As an 80s kid I have definitely been ruined by the karate kid, and "avoiding effort shock" (= avoiding reality = structured escapism) explains a lot of my life choices. Learning curves invariably turn out to be longer than I'm prepared to handle.
1
10
In terms of effort shock severity/reality-detail-encounter, the order is: words < math < programming < hardware skills of any sort. Topic came up because Lisa is teaching herself car repair.
1
4
Though I started my adult life as a mechanical engineer, I can safely say I have very little patience, and not much aptitude, for operating on levels of closeness to reality that have a lot of detail, and therefore have long-duration high-effort-shock learning curves.
1
6
It's not quite the same as not being detail oriented. I'm quite detail oriented in narrow ways when I want to be. It's being detail oriented when the details are *time-consuming* to master and deal with.
1
6
"Watching paint dry" is a good metaphor for this. You could say much of being reality-oriented is being willing to sit around "watching reality dry." Activities that fit this (passivities?) include debugging computer programs, which we talk about on the show.
1
7
What defeats me about debugging is the sheer disconnect between a) what seems wrong b) what turns out to be wrong c) the consequences of things being wrong. The only way to be a goo debugger is to develop the patience for troubleshooting. Watching reality dry.
1
11
Another way to think about it: being reality oriented means both being patient, and letting illusions of agency (which are strong at the level of words) drop away so you realize how little control you actually have over reality once you get down to literal nuts and bolts.
1
12
Reality doesn't care whether a missing comma means millions in lost revenue because a website is down, or no-big-deal because it's an obscure site nobody visits. Reality doesn't care whether a bug manifests to you as a mystery taking 10 hours, or obvious 2 second fix.
1
7
All it cares about is: you eventually get to adding that missing comma whether you get there in 2 seconds via luckily happening to notice it, or in 10 hours after spending hours and thousands of dollars exploring the wrong troubleshooting branch. It doesn't care if you're 8 or 80
1
2
And this isn't even the hardest case since debugging in programming still means working within the minds of other humans who wrote the compilers and operating systems. It is possible to get weirdly efficient at debugging code. Not so much reality as in atoms stuff.
1
5
Unlike code, nuts-and-bolts stuff has properties, features, and behaviors that weren't explicitly designed in by someone. So troubleshooting it is basically science. Leave your efficiency/productivity expectations based on delusions behind.
1
8
Note... not always true. There have been cases of weird software bugs in history that arise from strange hardware/software coupling effects. Especially at scale, when for eg. you're dealing with hundreds of hard-disks.
1
6