Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-05 · source-backed
Andrej Karpathy announced he's joining Anthropic, starting on the pretraining team. The post (X/Twitter) pulled close to 3 million views inside an hour, which tells you how much weight this one name still carries.
Here's why I can't stop thinking about it. This is the guy who coined "vibe coding." The OpenAI founding member who spent the last couple years teaching, building Eureka Labs, making the most-watched neural-net-from-scratch videos on the internet. The independent voice. And he's walking back into a frontier lab to do pretraining. Not tooling. Not education. Not an agent startup. Pretraining. The most capital-intensive, least glamorous, hardest-to-do-solo part of the entire stack.
The companion post is the part builders should sit with. He wrote that he's "never felt this much behind as a programmer," that his contributed bits are getting "increasingly sparse and far between," and that he could be 10X more powerful if he properly strung together the AI capabilities already sitting in front of him. Read that again. One of the best engineers alive is telling you the bottleneck isn't capability. It's orchestration. It's knowing how to wire the pieces together.
I've felt a version of this for months. The models can do more than I'm asking them to do, and the gap is on me, not them. The limiting factor in my own work shifted from "can the model do this" to "have I built the right harness around it." Karpathy saying it out loud, while also voting with his feet by going to pretraining, is a two-part signal: the frontier work is concentrating at the labs, and the leverage for the rest of us is in integration.
What to do about it: stop treating your AI tooling as a fixed thing you've already configured. Karpathy, with all his ability, thinks he's leaving 10X on the table by not stringing capabilities together. You almost certainly are too. Audit your actual workflow this week. Where are you hand-carrying context between tools that should be wired together? That's your 10X, sitting there.
Each link below shares sources, entities, or timing with this story.
Andrej Karpathy works at Anthropic / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Andrej Karpathy works at Anthropic); both cover Andrej Karpathy, Anthropic, Karpathy; reported by the same outlet (x.com).
Linked by a graph relationship (Andrej Karpathy works at Anthropic); both cover Andrej Karpathy, Anthropic, Karpathy; reported by the same outlet (x.com).
Andrej Karpathy uses Claude / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Andrej Karpathy uses Claude); both cover Andrej Karpathy, Anthropic, Karpathy; overlapping topics (anthropic, karpathy, team).
Andrej Karpathy uses Claude / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Andrej Karpathy uses Claude); both cover Anthropic, Twitter; reported by the same outlet (x.com).
Anthropic released MCP / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Anthropic released MCP); both cover Karpathy, Twitter; cite the same source (X/Twitter).
Andrej Karpathy uses Claude / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Andrej Karpathy uses Claude); both cover Andrej Karpathy, Karpathy, Twitter; reported by the same outlet (x.com).
Andrej Karpathy works at Anthropic / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Andrej Karpathy works at Anthropic); both cover Anthropic, Karpathy; overlapping topics (anthropic, capability, karpathy).
Linked by a graph relationship (Andrej Karpathy works at Anthropic); both cover Anthropic, Twitter; overlapping topics (anthropic, frontier, model).