index 0c98c62..d104763 100644
@@ -10,7 +10,7 @@ learning by building, not by studying. why making things teaches faster than rea
the best way to learn something is to build something with it. not read about it, not watch a tutorial, not take a course — build a real thing that forces you to confront the actual complexity.
-this isn't just my opinion. it's what the learning science supports: [[the-testing-effect]] shows that retrieval and application beat passive review. [[deliberate-practice]] shows that working at the edge of your ability beats comfortable repetition. building does both simultaneously.
+this isn't just my opinion. it's what the learning science supports: [[the-testing-effect]] shows that retrieval and application beat passive review. building does both simultaneously.
## why tutorials fail
@@ -40,22 +40,12 @@ my current approach: use AI for things i already understand (speed boost) and bu
this connects to [[critical-path]] — sometimes the critical path is building fast (use AI). sometimes the critical path is building understanding (do it yourself). knowing which one you're on matters.
-## projects as curriculum
-
-the best "curriculum" isn't a sequence of courses. it's a sequence of projects, each slightly beyond current skill:
-
-- project 1 forces you to learn X
-- project 2 uses X and forces you to learn Y
-- project 3 combines X and Y in a new context, plus Z
-
-this is natural [[spaced-repetition]] — you revisit earlier skills in new contexts, which is both review and [[transfer]]. each project is a test ([[the-testing-effect]]) of whether you actually learned the previous skills.
-
## the prototyping advantage
building something bad quickly teaches more than planning something perfect slowly. the prototype reveals what you actually don't know, which you can't discover by thinking about it. see [[startup-workflow]] — the lean methodology is basically building-to-learn applied to business.
## the role of documentation
-writing about what you built — like these wiki pages — is a second pass of learning. the [[testing-effect]] again: retrieving what you learned and organizing it in writing consolidates the knowledge. building is the first pass (learning through doing), writing is the second pass (learning through explaining).
+writing about what you built — like these wiki pages — is a second pass of learning. the [[testing-effect|the-testing-effect]] again: retrieving what you learned and organizing it in writing consolidates the knowledge. building is the first pass (learning through doing), writing is the second pass (learning through explaining).
this is why i use [[research-workflow]] as a complement to building, not a replacement. reading and research fill in the theoretical gaps that pure building misses — the "why" behind the "how."
\ No newline at end of file