Knowledge Dev is Andrew Altshuler's PKM methodology built on the premise that knowledge is fundamentally computable. It represents a post-skeuomorphic approach that argues traditional PKM concepts — notes, folders, commonplace books — are holdovers from analog thinking that constrain how we work with knowledge in digital environments.
Core Vocabulary
Knowledge Dev replaces familiar PKM metaphors with computational-first terminology:
- Flow — A non-linear attention path through knowledge space. Not a linear reading list or project plan, but the actual trajectory your mind takes as it moves between ideas, sources, and outputs.
- Attractors — Goals and tendencies that warp your exploration. Like gravitational fields, they pull your attention toward certain regions of knowledge space without dictating a rigid path.
- Threads — Parallel projects or lines of inquiry that compound when synchronized. The methodology emphasizes managing multiple threads simultaneously rather than serializing them.
- Enabling Constraints — Rules that paradoxically increase creative freedom. Examples: writing limits, capture protocols, time boxes. The constraint narrows the possibility space, making action easier.
- Protocols — Repeatable flow segments. Standardized sequences of knowledge work (capture, process, synthesize) that can be executed without decision fatigue.
- Filters — Criteria for what enters the system. Analogous to the resonance filter but framed computationally as input validation.
- Snapshots — Resumable states. Captured contexts that let you pause a thread and return to it later without losing momentum or mental state.
Paradigm Shift
The methodology's central claim is that analog-inspired metaphors actively limit digital knowledge work. A "note" implies a discrete object in a container. A "folder" implies hierarchical classification. Knowledge Dev argues for thinking in terms of flows, states, and transformations instead — concepts native to computation.
This is not merely a vocabulary change. It reframes PKM as a dynamic system rather than a collection management problem. Knowledge is not stored; it is processed. The system is not a library; it is a runtime environment.
Practical Relevance
Knowledge Dev's computational framing aligns with the direction of AI-augmented PKM and agentic knowledge management, where knowledge systems increasingly behave like programs — executing queries, transforming inputs, and producing outputs autonomously.
Key Points
- Rejects analog metaphors (notes, folders) as skeuomorphic constraints on digital knowledge work
- Introduces computational vocabulary: Flows, Attractors, Threads, Enabling Constraints, Protocols, Filters, Snapshots
- Frames PKM as a dynamic processing system rather than a static collection
- Emphasizes parallel threads and non-linear attention paths
- Anticipates AI-augmented and agentic knowledge management paradigms
Open Questions
- Is the computational vocabulary genuinely more powerful, or does it just replace one set of metaphors with another?
- How accessible is this methodology to non-technical knowledge workers?
- Does treating knowledge as computable risk losing the serendipitous, embodied aspects of thinking?
References
- Andrew Altshuler — Knowledge Dev methodology