Guillermo Rauch: Don't Read Every Line, Just Understand It

Rauch is not making the case for reading less — he is drawing a line against the popular advice that code no longer needs to be read at all. He says people who recommend skipping reading, comparing code to assembly, usually do not follow that advice themselves. His proposed middle ground is to have the agent generate the means of understanding, for instance by configuring Slack's MCP and writing into AGENTS.md that any change to the public API must be announced in Slack or Discord.

His view of speed carries the same theme. Tokens used and pull requests merged are good metrics, he says, but speed has a direction; he was struck by a founder who wanted to build his own email service and payments on top of agent ideas, calling it overreach. He adds that if you could build something in one shot, so could he — which is why the details that communicate intent and values need real work.

On tooling, he says what first drew him to Claude was how little was inside it, which he frames as a return to the Unix philosophy of combining small programs. His prediction that the future may be all Rust rests on the same forward-defense logic: agents writing code need strong guarantees, so safety should come from how code is made.