Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Flattening everything indiscriminately. The qualifier "when possible" in the title is load-bearing. Some domains have genuine hierarchical depth — legal codes, biological taxonomies, deeply nested technical architectures — where flattening would destroy the structural information that the.
Simpler hierarchies with fewer levels are easier to navigate and maintain.
Items nested inside a container share the context of that container.
Items nested inside a container share the context of that container.
Items nested inside a container share the context of that container.
Pick one active project in your knowledge system. List five items nested inside it. For each, ask: what context does this item inherit from its container that would be lost if I moved it to the root level? Write down the invisible context that nesting provides. You will likely find that the.
Nesting everything to the point where scope becomes a maze. When you nest seven levels deep, the context inherited at the bottom is so layered that you can no longer reconstruct which container contributed which meaning. The power of scope depends on legible containment — not maximum depth.
Items nested inside a container share the context of that container.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Choose a hierarchy you operate within — your organization, your note-taking system, your file structure, or your belief system. Identify three properties that propagate from a higher level to a lower level. For each one, answer: (1) Is this property explicitly stated or implicitly assumed? (2).
Blind inheritance — accepting every property that propagates from parent to child without examining whether it fits the child context. This shows up as teams following organizational processes that make no sense for their specific work, as note-takers applying folder-level tags to notes where.
Child items often inherit properties from their parent — be aware of what propagates.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Open your knowledge system and find a category, tag, or folder where at least one item doesn't fully belong — it inherited assumptions from its parent that don't hold. Write a one-sentence override statement on that item: 'Unlike [parent category], this item [specific difference].' Notice how the.
You notice exceptions but leave them implicit, trusting your memory to handle the special cases. Over time, the exceptions multiply. You stop trusting the parent category because too many children violate its assumptions, but you never articulate which assumptions break or why. The hierarchy.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.