the bottleneck Karpathy keeps pointing at isn't the model. it's the file you wrote three months ago telling it how to work. his whole framing: code isn't the verb anymore. > you express your will to agents 16 hours a day. > running more of them in parallel is the unlock. > and he drops this line halfway through, no fanfare: "now you can have optimization over the instructions." that's the sentence. the instructions are the new bottleneck. and almost nobody has a process for optimizing them. i built one for myself. it reads 100 of my past Claude Code sessions and rewrites my CLAUDE.md from what the transcripts show, not from what i thought i wrote. one Saturday morning later: a 38-line memory file. 73% of my old CLAUDE.md got deleted. most of it was one-off corrections that hardened into permanent rules months ago and were quietly steering every agent i ran. four behavior patterns surfaced that i had never written down. the loudest one: my prose corrections outnumber code corrections 8.2 to 1. that ratio was running silently through every session for 90 days. you don't need a smarter model. you need an instruction file that still describes how you actually work. listen to the podcast for the framing. open the article for the script that does the optimization.