We're All Addicted To Claude Code
These notes were generated by AI and may contain inaccuracies.
Using Claude Code in CLI enables debugging nested delayed jobs five levels deep, identifying bugs, writing tests to prevent recurrence. Hobbyists and small startups push coding agents to maximize speed due to limited runway. Larger companies have more to lose with established processes.
Welcome to another episode of the Light Cone podcast. Guest: Kelvin French Owen, first to create CodeX at OpenAI, previously started Segment (multi-billion dollar company, successful exit).
Host became addicted to Claude Code, likening it to recovering from 'manager mode' (catastrophic knee injury metaphor) via bionic knee replacement enabling five times faster running. Kelvin at forefront; CodeX pioneered ideas still used, continues evolving.
At OpenAI, worked on CodeX web project. Cursor used shim around GPT-3.5 in IDE; VS Code had CLI. Future vision: coding like talking to coworker—send question, get PR back. Now everyone uses CLIs like Claude Code or CodeX.
Everyone becoming managers; requires building trust in models, understanding their actions. Kelvin switched to Claude Code as daily driver (previously Cursor, then Claude Code with Opus).
Sign in to read the full notes
Get access to AI-generated notes, topic timestamps, and more.