index e01bff0..6845183 100644
@@ -12,7 +12,7 @@ joan didion said it plainly: "i write entirely to find out what i'm thinking, wh
this matches my experience exactly. i'll sit down to write about something i think i understand, and within a few paragraphs i'll hit a point where the sentence i'm writing doesn't quite work. the idea i had in my head was fuzzy, and the sentence demands precision. in the gap between the fuzzy idea and the precise sentence, new understanding forms.
-this is not a pleasant process. it's closer to [[debugging/rubber-duck-and-zoom-out|rubber duck debugging]] than to transcription. you're explaining your thinking to the page, and the page reveals that your thinking has holes.
+this is not a pleasant process. it's closer to [[rubber-duck-and-zoom-out|rubber duck debugging]] than to transcription. you're explaining your thinking to the page, and the page reveals that your thinking has holes.
## why it works
@@ -20,7 +20,7 @@ paul graham puts it well: "if writing down your ideas always makes them more pre
thinking feels fluid and complete in your head. you can hold a vague impression and feel like you understand something. writing forces serialization — you have to put one idea before another, make explicit connections, define terms. the constraints of language expose the gaps in thought.
-it's the same mechanism as [[debugging/assumptions-kill|assumption auditing]]. you think you know how the system works until you have to explain it step by step. the explaining surfaces the broken assumptions.
+it's the same mechanism as [[assumptions-kill|assumption auditing]]. you think you know how the system works until you have to explain it step by step. the explaining surfaces the broken assumptions.
## my experience with it