if we decouple the cost of caching into “was true but is false” and “was never true”, it may be that one dominates the other in likelihood. so maybe, the most efficient solution to the “cached thought” problem is not rethinking things, but ignoring most things by default. this, however, has the opportunity cost of false negatives.
i’ve personally found that i am very dependent on cached thoughts when learning/doing something new (not necessarily bad). like breadth over depth. what i do is try to force each cached thought to have a contradictory, or at least very different, twin.
e.g. though i have never coded in it, if i hear “C++”, i’ll (try to) think both “not worth it, too unsafe and errorprone” and “so worth it, speed and libraries”. whenever i don’t have enough data to have a strong opinion, i must say that i am ok with caching thoughts, as long as i know they are cached and i try to cache “contradictory twins” together.
indeed.
if we decouple the cost of caching into “was true but is false” and “was never true”, it may be that one dominates the other in likelihood. so maybe, the most efficient solution to the “cached thought” problem is not rethinking things, but ignoring most things by default. this, however, has the opportunity cost of false negatives.
i’ve personally found that i am very dependent on cached thoughts when learning/doing something new (not necessarily bad). like breadth over depth. what i do is try to force each cached thought to have a contradictory, or at least very different, twin.
e.g. though i have never coded in it, if i hear “C++”, i’ll (try to) think both “not worth it, too unsafe and errorprone” and “so worth it, speed and libraries”. whenever i don’t have enough data to have a strong opinion, i must say that i am ok with caching thoughts, as long as i know they are cached and i try to cache “contradictory twins” together.