Skip to content

Greg Foster

Graphite

  • 1 episode on Chain of Thought
  • 2 topics covered
  • 1 full transcript
  • Sep 2025 first on the show
Greg Foster

Greg Foster is the co-founder and CTO of Graphite, a code review platform used by teams like Cursor, Replit, and Snowflake. On Chain of Thought he argued that AI coding tools have shifted the bottleneck from writing code to reviewing it, and explained how "stacking" breaks large changes into reviewable pieces.

Cover art for After Code Gen: What Graphite Is Building for the Post-AI Dev Stack | Greg Foster

Latest episode with Greg Foster · EP 40

After Code Gen: What Graphite Is Building for the Post-AI Dev Stack | Greg Foster

Greg Foster, Graphite ·

Show notes & transcript → All listening options →

Episodes

What the conversations cover

These notes summarize the episodes featuring Greg Foster, including other speakers in panel conversations. Follow a source link to read the discussion in context.

EP 40 After Code Gen: What Graphite Is Building for the Post-AI Dev Stack | Greg Foster

  • Greg Foster frames AI’s impact on engineering as three waves: tab-complete (GitHub Copilot, then Cursor extending tab to fill multiple lines ahead); an IDE sidebar “director mode,” or the same pattern in Claude Code in the terminal where you send the model on small missions; and the most emergent — headless background agents you ping on Slack or GitHub, then get a pull request back hours later. Episode takeaways
  • As AI automates the inner loop of writing code, Greg argues the human outer loop is now the bottleneck — review, CI, merge queues, deployment, rollout monitoring. He points to tweets from the Anthropic team and others making the same case: it’s no longer code generation that’s the issue, but the DevOps and shipping practices around production. Episode takeaways
  • The strain shows up in numbers. Greg cites Facebook being quoted as doubling internal code changes per engineer over the past year, with another doubling expected soon, and says Graphite sees the same — code-change volume per engineer is “strictly up into the right” — pressuring both reviewers and merge systems. Episode takeaways

In their words

Then we merge it, but once you merge it, it's still not user facing. It's still not launched. We're going to have to rebuild a new artifact. We're going to have to gracefully roll that out onto production servers, checking all of our metrics and making sure we're not regressing something, spiking errors, causing a problem.

Greg Foster After Code Gen: What Graphite Is Building for the Post-AI Dev Stack | Greg Foster · 16:22

Transcript excerpts; ellipses mark omitted words. Some automatically selected quotes have filler words removed.