cool third point! i may hv oversold the point in my first comment. i too try to name things according to their thingness, but not exclusively.
to make a caricature of my research loop, i could describe it as
trying to find patterns that puzzle me (foraging),
distilling the pattern to its core structure and storing it in RemNote (catabolic pathway),
mentally trying to find new ways to apply the pattern
ie, propagating it, installing hooks (which I call isthmuses) into plausibly-related contexts such that new cryptically-related observations are more likely to trigger an insight (metaphor), allowing me to generalise further or discover smth i need to refactor
going abt business as usual, repeating 1-3 until unfolding branch meets unfolding branch from the other side, indicating i might hv found a profitable generalisation
an important consideration re keeping isthmuses alive enough to trigger connections: i don’t want to hv memorised this specific instantiation of the pattern so it’s crystal clear. if it fits neatly into a slot and it’s comfortable w its assigned niche, it’s unlikely to trigger in novel situations. imprecision/fuzziness is good when the concept is still in exploratory phase (and not primarily tool-stage).
fix everything
loop is often bottlenecked by the high cost of refactoring anything. i rly wish i could find a general algorithm/strategy for refactoring complex systems like this, or a clever approach to building that minimises/eliminates the need.
the optimal conlang isn’t a new set of words. it’s a new set of practices for naming things, unnaming things, generalising & specialising, communal decision-processes for resolving conflicts, neat meta-structures that minimise cost of refactoring (somehow), enabling eager contributors w minimal overhead & risk of degeneration, etc.
the optimal conlang isn’t a new set of words. it’s a new set of practices for naming things, unnaming things, generalising & specialising, communal decision-processes for resolving conflicts, neat meta-structures that minimise cost of refactoring (somehow), enabling eager contributors w minimal overhead & risk of degeneration, etc.
cool third point! i may hv oversold the point in my first comment. i too try to name things according to their thingness, but not exclusively.
to make a caricature of my research loop, i could describe it as
trying to find patterns that puzzle me (foraging),
distilling the pattern to its core structure and storing it in RemNote (catabolic pathway),
mentally trying to find new ways to apply the pattern
ie, propagating it, installing hooks (which I call isthmuses) into plausibly-related contexts such that new cryptically-related observations are more likely to trigger an insight (metaphor), allowing me to generalise further or discover smth i need to refactor
going abt business as usual, repeating 1-3 until unfolding branch meets unfolding branch from the other side, indicating i might hv found a profitable generalisation
an important consideration re keeping isthmuses alive enough to trigger connections: i don’t want to hv memorised this specific instantiation of the pattern so it’s crystal clear. if it fits neatly into a slot and it’s comfortable w its assigned niche, it’s unlikely to trigger in novel situations. imprecision/fuzziness is good when the concept is still in exploratory phase (and not primarily tool-stage).
fix everything
loop is often bottlenecked by the high cost of refactoring anything. i rly wish i could find a general algorithm/strategy for refactoring complex systems like this, or a clever approach to building that minimises/eliminates the need.
the optimal conlang isn’t a new set of words. it’s a new set of practices for naming things, unnaming things, generalising & specialising, communal decision-processes for resolving conflicts, neat meta-structures that minimise cost of refactoring (somehow), enabling eager contributors w minimal overhead & risk of degeneration, etc.
Absolutely.