Help. Claude is building itself.

Max Haining

Max Haining

7 Jun 20265 min read

Article cover image.

Claude writes most of Claude now.

I mean that literally. Anthropic announced this week that Claude writes more than 80% of the code going into Anthropic's own systems. Before they launched Claude Code early last year, it was almost none. In the same post, they said maybe we should think about slowing down before the thing writing their code gets good enough to build the next version of itself.

The internet of course replied with memes.

Article image.

Over on Reddit, people reacted with "Okay and..?", under a pile of people pointing out that bragging about lines of code is like weighing a plane to check how the build is going.

I get the shrug, we’ve heard big AI claims before. But if AI is writing the code, doing the admin, drafting the deck.. what's the part of your job that's still yours now?

From the recent layoffs, I noticed that the people who seemed calmest weren't the ones with the slickest setup. They’re just the one who have been doing real work with AI every day so for them the answer to "what's mine" was obvious. For others, it's the question of the year.

Window into the future

There's an answer everyone's landed on. Dylan Field, who runs Figma, put it this week: when execution's cheap, design and creativity are the edge. Swap in "taste," swap in "judgment". That's most of my feed right now. The doing is the easy part, your value is knowing what's worth doing.

Article image.

I buy a version of it. I've built part of a company on it. But it caught on so fast that "taste is the edge" has become its own kind of slop because nobody says what “taste” actually looks like.

Since agentic AI turned up, app releases have shot up but the apps people use stayed flat, and reviews even dropped. There's even a study on it, with a title that gives it away: Writing Code vs. Shipping Code.

The researchers have a name for it: the weak link. AI crushed the easy part like building, so all the slow human parts that come after like getting anyone to use these apps became the bottleneck. Cheap execution didn't hand everyone an edge. It just shows how important distribution is.

The thing that turns AI from a fast typist into better work is knowing what to ask for, catching it when it's wrong, and reworking it until it's yours. You build that by doing the work, not by watching AI do it. a16z had a piece this week about handing a dentist's insurance paperwork to an agent. Fair enough, nobody trains for years to chase reimbursements. But the junior stuck with that job was also learning how the business actually works. Hand it all over on day one and the judgment everyone's calling the edge never gets the chance to form.

Which is how you get what people are calling AI dumping: someone forwards you a doc Claude spun up and you can't tell if a brain was ever in the room. I do it too, when I'm tired. The fix isn't clever. Treat anything AI hands you like a first draft from a sharp intern, and never ship it unread. Argue with it. Cut the lines that sound smart and say nothing. Your name's on it, so the thinking has to live somewhere.

It's also why your feed reads like it was written by one tired robot. LinkedIn said this week it'll start burying posts that sound machine-made including the "it's not X, it's Y" move, now officially a tell (a sentence shape I'll be avoiding for the rest of my life). Ethan Mollick caught the everyday version: it's bleak to open an app and hit a menu full of Claudisms. When everyone runs their thinking through the same model, polished writing stops being proof that anyone thought. And proof is all it ever was.

Article image.

And it's about to get blurrier. OpenAI gave ChatGPT a memory upgrade this week (they’re calling it dreaming) so the more you use it, the more it answers like it knows you. Want to see that line? Drop the same prompt into a logged-out incognito window and compare. The difference is how much was just it having learned you.

So you have to decide what stays yours on purpose.

The rule I've landed on, stolen from Alex Lieberman, who broke down his content process this week: keep the first mile and the final mile, give AI the middle. First mile is deciding what's worth doing and handing over the context. Final mile is the final call. The boring 70% in between, let the machine have it.

Article image.

So this week: pick one thing you've been handing over whole. Write the messy first draft yourself, let AI clean it up, then do the last read by hand. Keep the two ends. That's the part you'll want to still be good at next year.

Share this

Ready to build real AI capability

Get weekly insights on adoption, team rituals, and practical workflows — straight to your inbox.

We respect your inbox. Unsubscribe anytime.

Person holding a lightbulb with an idea.