ATRIUMsearch → argument graph
Article · 2026-07-21 · 6 moments

A Fireside Chat with Cat and Thariq from the Claude Code team

Earlier this month I hosted a fireside chat session at the AI Engineer World's Fair with Cat Wu and Thariq Shihipar from Anthropic's Claude Code team. We talked about Claude Code, Claude Tag, Fable, coding agent security, evals, tool design, and how Anthropic use these tools themselves. The full video of the session is now available on YouTube. Below is an edited copy of the transcript, with extra links and my own bolded highlights. A few top-level notes if you don't want to watch the video ✦ AI generated

timeline · colored by role

01
Claim

The timeline between having an idea and building it has collapsed from months to weeks, so engineers need stronger product taste and business sense.

Cat Wu describes how the speed of AI-assisted coding has compressed the idea-to-implementation cycle, making product judgment more valuable than execution skill in most domains.

transcript

Cat Wu: Two years ago it was pretty typical for a product manager to go talk to a bunch of customers, align over the course of six months with cross-functional teams on some PRD, and write a thorough spec on exactly how we'll implement this before the first line of code gets written. Now things are completely turned the opposite way. For a lot of engineers, the push I would give to folks in the room is to develop more of your business sense and product sense on what it is we should build, because the timeline between having an idea and building it is so much shorter — it's down from six to twelve months to maybe even a week.

provides context · 2

02
Claim

Rewrites are now good, contrary to the conventional wisdom from The Mythical Man-Month.

Thariq Shihipar argues that the old rule against rewrites no longer applies, because AI tools can distill a codebase's spec into a new implementation and force better test coverage.

transcript

Thariq Shihipar: All the Mythical Man-Month stuff — never rewrite — I'm pro-rewriting now. If you have a good test suite — and I think the rewrite actually forces you to make sure you have a good test suite — but I think what people undercount is that a codebase is a spec, and maybe it's the only copy of the spec that you have, because no one knows every branching part of the codebase. You can take this as an artifact and distill it or create other versions of it.

explains mechanism · 1provides context · 1

03
Mechanism

Anthropic ships features internally first and only releases them publicly if they demonstrate user retention with that cohort.

Cat Wu explains Anthropic's dogfooding culture: every feature is tested internally against a retention bar before public release, which forces polish and prioritization.

transcript

Cat Wu: One is we dogfood our products every single day. Whenever there's something we want to be able to do in our products that we're not able to, instead of finding a different solution we fix our product so it can support that case. We have a very heavy dogfooding culture internally. Before we share our products with everyone in the world, we share them with everyone within Anthropic, and with some early customers who give us very honest feedback about it — the more brutal the better — and we iterate until people love it.

04
Mechanism

The Claude Code system prompt was reduced by 80% because adding examples and 'do not do this' rules constrains newer models and can confuse them.

Thariq and Cat explain that for frontier models like Opus 4.8 and Fable, fewer instructions and more context produce better results — examples and hard constraints that worked for older models now reduce quality.

transcript

Thariq Shihipar: One of the patterns we saw was that we were over-constraining Claude. The initial, maybe Opus 4-ish models wanted a lot of examples, and removing examples was extremely helpful, because it was just more creative than the examples we gave it. The other thing we did is try to give it more context and fewer 'do not do this' instructions, because that's a very strong impulse for Claude, and especially if it conflicts with user instructions later on, that can be extremely confusing to Claude.

explains mechanism · 1

05
Claim

The way to offset the sense of grief or loss from AI taking over software engineering work is to be more ambitious about what you build.

Thariq Shihipar argues that if you only try to do the same work you did before LLMs, automation feels like a loss, but raising your ambition — doing the bigger thing — turns that loss into opportunity.

transcript

Thariq Shihipar: On your point about loss: I think this is real. If you're only trying to do the same work you were doing before LLMs, and now it's a prompt, it is, I think, kind of a sad feeling. And the way you offset that is by being more ambitious. I think Jared is such a good example — he hand-wrote all of the Zig code in his Oakland apartment in about a year, barely left his house, and had so much fun doing that. Now I see him rewrite all of Bun into Rust and he's having so much fun doing that — it's so much more ambitious, and that's how he offsets it.

extends · 1supports · 1

06
Data

Claude Tag lands 65% of the product engineering PRs for the Claude Code team.

Cat Wu reveals that Claude Tag, the team's Slack-integrated coding agent, now handles a majority of the product engineering team's pull requests.

transcript

Cat Wu: Claude Tag currently lands 65% of our product PRs right now. And this is a huge shift; this is more than 50% of our PRs. The way we see people split work between Claude Code and Claude Tag is: Claude Code is still the best place for your most complex tasks, when you're interactively iterating with the agent. But Claude Tag is great for having it work proactively on your behalf, so you no longer need to manually kick off Claude Code for all the bug reports that come up for features you're working on.

Highlight slides
Related episodes