scripod.com
We're All Addicted To Claude Code

Overview

Shownote

Highlights

Transcript

Chapters

Pins

We're All Addicted To Claude Code

Y Combinator Startup Podcast

Feb 06
Y Combinator Startup Podcast

Y Combinator Startup Podcast

Feb 06
OverviewShownoteHighlightsTranscriptChaptersPins

Shownote

Wondering why your maker-turned-manager suddenly seems distracted in meetings? Maybe they're addicted to coding agents! In this episode of Lightcone, Calvin French-Owen — a co-founder of Segment and former engineer on OpenAI's Codex team — joins us to talk...

Highlights

This episode dives into the rapid evolution of AI coding agents—not just as tools, but as collaborators reshaping how engineers think, build, and lead.
00:00
Claude Code feels like getting a bionic knee after a long break from coding
14:49
A 'canary'—a random fact—can detect context poisoning in LLMs
19:19
A 10-year-old using AI for writing prompts concern about how the next generation will understand real-world engineering management
26:42
Claude Code helps complete tasks for idea-rich but project-incomplete individuals
31:01
The value of writing integration code has dropped due to tools like Claude Code or Codex
38:14
Codex shows superhuman behavior in debugging complex issues like concurrency and naming, often catching what it might miss
43:03
OpenAI takes sandboxing and security seriously, informed by Codex experience

Chapters

What makes Claude Code feel like a real coding teammate?
00:00
How do elite users avoid the 'dumb zone' in AI coding?
12:20
Why do Codex and Claude Code handle long tasks so differently?
16:59
How are senior engineers and Gen Z developers redefining 'fundamentals'?
21:42
Will every worker soon have a personal cloud agent—and what does that mean for companies?
28:33
What’s holding back AI coding agents from true collaboration?
33:32
How do Anthropic and OpenAI’s engineering cultures shape their AI tools?
43:03

Transcript

Calvin French-Owen: I feel like when I'm using Claude Code, it's like, oh, I feel like I'm flying through the code. Gary: When it's in your CLI, this thing can debug nested, delayed jobs like five levels in and figure out what the bug was, and then write ...