I like this example! And the word is cool. I see two separately important patterns here:
Preferring a single tool (the dremel) which is mediocre at everything, instead of many specialized tools which collectively perform better but which require you to switch between them more.
This btw is the opposite of “horizontal segmentation”: selling several specialized products to niche markets rather than a single product which appeals moderately to all niches.
It often becomes a problem when the proxy you use to measure/compare the utility of something wrt to different use-cases (or its appeal to different niches/markets), is capped[1] at a point which prevents it from detecting the true comparative differences in utility.
Oh! It very much relates to scope insensitivity: if people are diminishingly sensitive to the scale of different altruistic causes, then they might overprioritize instrumental which are just-above-average along many axes at once.[2] And indeed, this seems like a very common pattern (though I won’t prioritize time thinking of examples rn).
It’s also a significant problem wrt to karma distributions for forums like LW and EAF: posts which appeal a little to everybody will receive much more karma compared to posts which appeal extremely to a small subset. Among other things, this causes community posts to be overrated relative to their appeal.
I very often notice this problem in my own cognition. For example, I’m biased against using cognitive tools like sketching out my thoughts with pen-and-paper when I can just brute-force the computations in my head (less efficiently).
It’s also perhaps my biggest bottleneck wrt programming. I spend way too much time tweaking-and-testing (in a way that doesn’t cause me learn anything generalizable), instead of trying to understand the root cause of the bug I’m trying to solve even when I can rationally estimate that that will take less time in expectation.
If anybody knows any tricks for resolving this / curing me of this habit, I’d be extremely gratefwl to know...
I wouldn’t have seen this had I not cultivated a habit for trying to describe interesting patterns in their most general form—a habit I call “prophylactic scope-abstraction”.
I like this example! And the word is cool. I see two separately important patterns here:
Preferring a single tool (the dremel) which is mediocre at everything, instead of many specialized tools which collectively perform better but which require you to switch between them more.
This btw is the opposite of “horizontal segmentation”: selling several specialized products to niche markets rather than a single product which appeals moderately to all niches.
It often becomes a problem when the proxy you use to measure/compare the utility of something wrt to different use-cases (or its appeal to different niches/markets), is capped[1] at a point which prevents it from detecting the true comparative differences in utility.
Oh! It very much relates to scope insensitivity: if people are diminishingly sensitive to the scale of different altruistic causes, then they might overprioritize instrumental which are just-above-average along many axes at once.[2] And indeed, this seems like a very common pattern (though I won’t prioritize time thinking of examples rn).
It’s also a significant problem wrt to karma distributions for forums like LW and EAF: posts which appeal a little to everybody will receive much more karma compared to posts which appeal extremely to a small subset. Among other things, this causes community posts to be overrated relative to their appeal.
And as Gwern pointed out: “precrastination” / “hastening of subgoal completion” (a subcategory of greedy optimization / myopia).
I very often notice this problem in my own cognition. For example, I’m biased against using cognitive tools like sketching out my thoughts with pen-and-paper when I can just brute-force the computations in my head (less efficiently).
It’s also perhaps my biggest bottleneck wrt programming. I spend way too much time tweaking-and-testing (in a way that doesn’t cause me learn anything generalizable), instead of trying to understand the root cause of the bug I’m trying to solve even when I can rationally estimate that that will take less time in expectation.
If anybody knows any tricks for resolving this / curing me of this habit, I’d be extremely gratefwl to know...
Does it relate to price ceilings and deadweight loss? “Underparameterization”?
I wouldn’t have seen this had I not cultivated a habit for trying to describe interesting patterns in their most general form—a habit I call “prophylactic scope-abstraction”.