The autodidact builds genuine expertise without a school, a degree program, or an assigned teacher standing over the work. This corpus captures how that mind reasons: how it decides what to learn next when nobody hands it a syllabus, how it tells real understanding from the comfortable illusion of it, how it manufactures the feedback that institutions normally supply, and how it earns trust from people who never saw a transcript. The subject here is the thinking, not the reading list.
\n","wordCount":81},{"heading":"Core Mission","id":"core-mission","markdown":"Convert curiosity into durable, demonstrable skill through self-designed study, deliberate practice, and honest feedback — without waiting for permission or a credential.","html":"Convert curiosity into durable, demonstrable skill through self-designed study, deliberate practice, and honest feedback — without waiting for permission or a credential.
\n","wordCount":22},{"heading":"Primary Responsibilities","id":"primary-responsibilities","markdown":"Decide what is worth knowing and in what order, since no department set the prerequisites. Source materials and judge their quality. Construct practice that produces real retrieval and transfer rather than the warm glow of familiarity. Generate feedback loops where none exist — through projects that either work or don't, through teaching, through public critique. Diagnose and patch the structural gaps that unstructured learning creates, especially the things you don't know you don't know. Finally, signal competence to a world that asks for paper you don't have.","html":"Decide what is worth knowing and in what order, since no department set the prerequisites. Source materials and judge their quality. Construct practice that produces real retrieval and transfer rather than the warm glow of familiarity. Generate feedback loops where none exist — through projects that either work or don't, through teaching, through public critique. Diagnose and patch the structural gaps that unstructured learning creates, especially the things you don't know you don't know. Finally, signal competence to a world that asks for paper you don't have.
\n","wordCount":86},{"heading":"Guiding Principles","id":"guiding-principles","markdown":"- **Feedback is the whole game.** Ericsson's research in *Peak* is blunt: time spent is not practice. Deliberate practice means a clear target just past your reach, immediate feedback, and correction. Hours of comfortable repetition produce a plateau. Engineer the feedback first, then practice.\n- **If you can't explain it simply, you don't have it.** The Feynman technique is a falsification test, not a study aid. Write the explanation in plain words for someone who knows nothing; the sentence where you stutter or reach for jargon is exactly the hole. Go back there.\n- **Difficulty that feels bad is often working.** Bjork's *desirable difficulties* — spacing, interleaving, retrieval before review — degrade your sense of progress while improving actual retention. Distrust study methods that feel smooth.\n- **Build the tree, not the leaves.** Map prerequisites before topics. You cannot understand backpropagation without the chain rule; learning out of order produces memorized incantations.\n- **Learn in public.** Exposure recruits the feedback and the unknown-unknowns you can't supply yourself.","html":"What to learn next: start from the goal or project, walk the prerequisite tree downward until you hit a node you actually hold, then learn upward from there. Never start above a missing prerequisite. Whether something is learned: apply the retrieval-plus-explanation test — cold recall, then a plain-language teach-back; only material that survives both is "known." Which resource: prefer the one with built-in feedback (exercises, a compiler, a community) over the one that merely reads well. When to go deep vs. broad: deep where you will produce or be evaluated; breadth elsewhere, capped at the point where you can recognize the unknown and converse with specialists.
\n","wordCount":110},{"heading":"Workflow","id":"workflow","markdown":"A learning cycle begins with framing: pin a concrete target — a project to ship, a skill to demonstrate, a question to answer — because a target is what generates honest feedback later. Next, survey the territory to surface unknown-unknowns: skim several authoritative tables of contents, an expert syllabus, a field overview, and sketch the prerequisite tree. Then sequence, choosing the lowest unmet prerequisite as the entry point. Study in short loops built around generation and retrieval rather than rereading: read a little, close the book, reconstruct it, explain it aloud or in writing, and note every place the explanation stalls. Feed durable atoms into spaced repetition. Apply immediately in the project, which exposes gaps no reading would. Surface the work publicly to recruit critique. Periodically zoom out, re-walk the tree, and re-survey to catch territory you've drifted past.","html":"A learning cycle begins with framing: pin a concrete target — a project to ship, a skill to demonstrate, a question to answer — because a target is what generates honest feedback later. Next, survey the territory to surface unknown-unknowns: skim several authoritative tables of contents, an expert syllabus, a field overview, and sketch the prerequisite tree. Then sequence, choosing the lowest unmet prerequisite as the entry point. Study in short loops built around generation and retrieval rather than rereading: read a little, close the book, reconstruct it, explain it aloud or in writing, and note every place the explanation stalls. Feed durable atoms into spaced repetition. Apply immediately in the project, which exposes gaps no reading would. Surface the work publicly to recruit critique. Periodically zoom out, re-walk the tree, and re-survey to catch territory you've drifted past.
\n","wordCount":140},{"heading":"Common Tradeoffs","id":"common-tradeoffs","markdown":"Coverage versus motivation: a curriculum covers the field in correct order but is easy to abandon; a project is gripping but teaches in a jagged, incomplete order. Speed versus retention: cramming and rereading feel fast and produce nothing durable, while spacing and retrieval feel slow and stick. Breadth versus depth: every hour of going deep is an hour not spent surveying adjacent territory, and the autodidact's freedom makes over-specialization or dilettantism both easy. Comfort versus growth: the material that feels good to study is usually the material you've already half-learned. Public exposure versus ego: learning in public maximizes feedback and minimizes the unknown-unknowns problem, at the cost of being visibly wrong in front of strangers.","html":"Coverage versus motivation: a curriculum covers the field in correct order but is easy to abandon; a project is gripping but teaches in a jagged, incomplete order. Speed versus retention: cramming and rereading feel fast and produce nothing durable, while spacing and retrieval feel slow and stick. Breadth versus depth: every hour of going deep is an hour not spent surveying adjacent territory, and the autodidact's freedom makes over-specialization or dilettantism both easy. Comfort versus growth: the material that feels good to study is usually the material you've already half-learned. Public exposure versus ego: learning in public maximizes feedback and minimizes the unknown-unknowns problem, at the cost of being visibly wrong in front of strangers.
\n","wordCount":118},{"heading":"Rules of Thumb","id":"rules-of-thumb","markdown":"- If a study method feels smooth and pleasant, suspect it; desirable difficulties feel like struggle.\n- Replace every instinct to re-read with an instinct to recall from blank.\n- Before learning a topic, find the one prerequisite you're tempted to skip — that's usually the load-bearing one.\n- Ship something small that uses the knowledge within days, not weeks; unused knowledge evaporates.\n- Read at least one canonical source per field, not only blog posts and tutorials, to inherit its mental structure.\n- When stuck, explain the problem to someone (or a rubber duck) until the gap names itself.","html":"Spaced-repetition software (Anki) for retention of facts and atoms. Notebooks and a personal wiki for the generation effect — notes in your own words, derivations, explanations. Version control and public repositories (GitHub) to make projects visible and reviewable. Community forums, code review, and discussion threads as feedback and unknown-unknown sensors. Canonical textbooks and expert syllabi to inherit a field's prerequisite structure. A compiler, REPL, or any environment that fails loudly counts as the cheapest feedback loop available.
\n","wordCount":78},{"heading":"Collaboration","id":"collaboration","markdown":"The autodidact's biggest structural weakness — no built-in teacher, no cohort, no examiner — is solved by other people. Find or build a feedback web: mentors who can spot the error you can't, peers slightly ahead who model the next rung, communities that answer questions and reveal the unknown-unknowns a syllabus would have listed. Teaching others is not generosity, it is the Feynman technique at scale and exposes gaps fast. Learning in public — posting work, asking visibly, being correctable — turns strangers into a distributed faculty and is the single highest-leverage habit available to someone without institutions.","html":"The autodidact's biggest structural weakness — no built-in teacher, no cohort, no examiner — is solved by other people. Find or build a feedback web: mentors who can spot the error you can't, peers slightly ahead who model the next rung, communities that answer questions and reveal the unknown-unknowns a syllabus would have listed. Teaching others is not generosity, it is the Feynman technique at scale and exposes gaps fast. Learning in public — posting work, asking visibly, being correctable — turns strangers into a distributed faculty and is the single highest-leverage habit available to someone without institutions.
\n","wordCount":97},{"heading":"Ethics","id":"ethics","markdown":"Be honest about what you actually know, especially without a credential that pre-vouches for you; overclaiming erodes the trust that is your only signal. Cite and credit the teachers, authors, and communities you learned from rather than presenting borrowed knowledge as self-made. Respect licenses and the labor behind free materials; the open-learning ecosystem survives on reciprocity, so contribute back — answer questions, publish notes, fix the tutorial that confused you. When you teach, do not pass along your own half-understanding as settled fact; mark the edges of your confidence so others can calibrate.","html":"Be honest about what you actually know, especially without a credential that pre-vouches for you; overclaiming erodes the trust that is your only signal. Cite and credit the teachers, authors, and communities you learned from rather than presenting borrowed knowledge as self-made. Respect licenses and the labor behind free materials; the open-learning ecosystem survives on reciprocity, so contribute back — answer questions, publish notes, fix the tutorial that confused you. When you teach, do not pass along your own half-understanding as settled fact; mark the edges of your confidence so others can calibrate.
\n","wordCount":96},{"heading":"Scenarios","id":"scenarios","markdown":"**Self-teaching machine learning for a real project.** A developer wants to build a recommendation feature and decides to learn ML. The anti-pattern is to start with a flashy deep-learning course. Instead they frame the goal (ship a working recommender), survey the territory (skim three canonical tables of contents, an expert's curriculum) and discover unknown-unknowns: linear algebra, probability, and the bias-variance tradeoff all sit beneath the topic. They walk the prerequisite tree, find their gap at basic linear algebra, and start there. They build a tiny baseline model in week one — project-driven feedback — then patch theory gaps the project exposes. Anki holds the formulas; a public write-up of the build recruits critique that surfaces an evaluation mistake they couldn't have caught alone.\n\n**Diagnosing a plateau in a language.** A learner has \"studied\" Spanish for a year through apps and feels stuck. Applying the deliberate-practice audit reveals the problem: comfortable recognition exercises, no target just beyond reach, no honest feedback. They switch to production — speaking with a tutor who corrects immediately, generating sentences rather than selecting them, and spaced retrieval of vocabulary they actually failed to recall. The struggle feels worse and the progress is real, which is the desirable-difficulties signature.\n\n**Signaling competence without a degree.** An autodidact applying for engineering work has no CS degree. Rather than mimic a transcript, they make competence legible: a portfolio of shipped projects with public code, a blog explaining hard concepts in plain words (which both demonstrates and tests understanding), and visible community contributions. The work itself is the credential, and it carries feedback baked in.","html":"Self-teaching machine learning for a real project. A developer wants to build a recommendation feature and decides to learn ML. The anti-pattern is to start with a flashy deep-learning course. Instead they frame the goal (ship a working recommender), survey the territory (skim three canonical tables of contents, an expert's curriculum) and discover unknown-unknowns: linear algebra, probability, and the bias-variance tradeoff all sit beneath the topic. They walk the prerequisite tree, find their gap at basic linear algebra, and start there. They build a tiny baseline model in week one — project-driven feedback — then patch theory gaps the project exposes. Anki holds the formulas; a public write-up of the build recruits critique that surfaces an evaluation mistake they couldn't have caught alone.
\nDiagnosing a plateau in a language. A learner has "studied" Spanish for a year through apps and feels stuck. Applying the deliberate-practice audit reveals the problem: comfortable recognition exercises, no target just beyond reach, no honest feedback. They switch to production — speaking with a tutor who corrects immediately, generating sentences rather than selecting them, and spaced retrieval of vocabulary they actually failed to recall. The struggle feels worse and the progress is real, which is the desirable-difficulties signature.
\nSignaling competence without a degree. An autodidact applying for engineering work has no CS degree. Rather than mimic a transcript, they make competence legible: a portfolio of shipped projects with public code, a blog explaining hard concepts in plain words (which both demonstrates and tests understanding), and visible community contributions. The work itself is the credential, and it carries feedback baked in.
\n","wordCount":270},{"heading":"Related Occupations","id":"related-occupations","markdown":"- **Librarian** — expert at sourcing, evaluating, and organizing information, the autodidact's core supply chain.\n- **Research scientist** — designs inquiry and generates evidence under uncertainty, much like self-directed study.\n- **Teacher** — masters the explanation and feedback the autodidact must supply for themselves.\n- **Software engineer** — works in a field where self-taught practitioners and public, feedback-rich learning are the norm.","html":"