Philip Su has spent two decades at the highest levels of software engineering — Microsoft, Meta (where he reached Distinguished Engineer, IC9), OpenAI, and now building his own product solo with AI. In this episode, he makes a provocative case: the individual contributor role as we know it is over, code reviews are becoming a liability, and the best engineers are already managing AI agents instead of writing code themselves.
From Dirty Fuel to Clean Fuel — Philip’s Unusual Career Arc
“When I look at those employment opportunities, I feel like maybe one theme is moving from what people are calling dirty fuel into clean fuel — meaning, what sorts of things motivate you? Dirty fuel would be something like, my parents never complimented me and so now I’m going to drive and prove them wrong. Clean fuel would be, I’ve always loved computer science and I’m here to do it.”
Philip’s path through tech is anything but linear. He became a dev manager at Microsoft before 30, then spent the next decade comfortable but stagnating — until he interviewed at Google, Amazon, and Meta and received offers three levels below his Microsoft position. That fear drove him to Facebook in 2010, when it had just 500 employees and people were still saying Friendster would come back. He scaled the London engineering office from a dozen engineers to 500+, then stepped away entirely.
Depression led him to take a warehouse floor job at Amazon during Peak 2021 — 11-hour shifts, moving six tons of packages a day with his arms. He documented the experience in his Peak Salvation podcast. The lessons were sharp: incentives shape behavior (warehouse workers got raises based on tenure, not performance, which incentivized doing the minimum), changing machines that are already operating is brutally hard, and misplaced pride is dangerous. Workers on the floor laughed when robots failed. Philip’s takeaway was the opposite: “Do you think the corporate robot designers just gave up and went home? Or do you think V2 is coming and V3 is coming until finally it takes over your job?” He later joined OpenAI as an individual contributor before leaving to build Superphonic, an AI-powered podcast player.
No More Code Reviews: The Lights-Out Codebase
“I grew up in the 80s and 90s. Today, even Stockfish, free on your phone, can beat the world’s best chess masters. What if I proposed to you today that you should take that free software, and when you’re playing some other player, have a human chess master review every move, just to make sure the AI hasn’t made a mistake? I would think that was patently ridiculous.”
Philip borrows the concept of “lights-out” from data centers that run with zero human workers and applies it to codebases — code where no human ever sees or edits the source. His pragmatic argument is simple: if developers are producing 5x to 20x more code per day, where is the time for code review coming from? But his real argument goes deeper. He draws a parallel to chess engines: we’ve already accepted that machines play better chess than humans. He believes we’ll reach the same point with code, and when we do, human intervention will be seen as a risk, not a safeguard. Philip is clear he’s not arguing for lights-out codebases today — he’s arguing about the direction. As he put it in his Substack essay “No More Code Reviews: Lights-Out Codebases Ahead”: we cannot aspire to build bigger things if the fundamental requirement is that one human has understood every last line of code in the codebase. The Windows codebase was 50 million lines 26 years ago — even distinguished engineers operated at the level of boxes and lines, not individual code.
AI Killed the Individual Contributor
“At the ground level, my premise is that if I look at my workday on Superphonic right now, I am mostly spending my time doing what classic engineering managers do. I am setting priorities for the team of agents I have. I am reviewing the code of the agents. I am deciding between agents who conflict in recommendations. I’m resolving conflict — I’m doing all the classic manager things.”
In his widely discussed essay “AI Killed the Individual Contributor”, Philip argues that maximizing productivity with AI now requires engineers to spend their time on management tasks: setting priorities, resolving conflicts, delegating to agents, reviewing output, and giving feedback. The IC role isn’t disappearing because AI codes better — it’s disappearing because the highest-leverage use of an engineer’s time has shifted from writing code to orchestrating the systems that write code. Philip has been using Claude Code CLI primarily, after switching from Cursor, and for the last four months has not personally touched a single line of code while producing 40 hours a week of output. He frames the transition through an offshoring analogy: early outsourcing gave you worse code, but cheaper. AI is the same trade-off today — except the quality ceiling is rising fast. The engineers who thrive will be the ones who learned to let go of the keyboard and focus on judgment, direction, and taste.
What Breaks When Developers Are 20x More Productive
“If they produce 20x, it is morally equivalent to saying, suddenly, you have 100 software developers, one PM, and one designer. I think the breaks are very clear when you think about it that way.”
Philip’s framing cuts through the productivity hype. Take a typical team — 5 engineers, 1 PM, 1 designer. At 20x output, that’s functionally 100 engineers with the same PM and designer. The bottleneck shifts instantly to planning, coordination, and product judgment. Philip’s answer to what companies should do with the surplus capacity is telling: most CEOs are cutting developers to reap efficiencies. Philip thinks that’s backwards. He invokes The Mythical Man-Month: you produce far more customer value per employee by reducing headcount than by scaling output, because human coordination and politics are massive efficiency drains. But the smarter play is using the capacity to tackle the next three things on your strategic roadmap, not just cutting costs. He draws a parallel to the dot-com era — directionally right, wrong about timing and winners. With AI, he believes most people are wrong about timing in the other direction: they think it will take years, but the improvements are compounding faster than anyone expects.
Do the Work Yourself First
“The one resource that I would recommend people do is trust no one, do the work yourself. Every person that just brags they vibe coded Tetris, or every person that says I changed my Claude.md to do this — all of this is Wild West. Your best resource is to hands-on build real products with the AI.”
For Scrum Masters and agile coaches helping teams adopt AI tools, Philip’s warning is clear: don’t treat AI as just another developer on the team. The integration requires rethinking how work is structured, how quality is assured, and what it means to be an engineer. Teams that bolt AI onto existing workflows without changing the underlying process will get marginal gains at best. Philip’s practical advice is to stop reading about AI and start building with it. Use the leading-edge tools, pay for the tokens, and see what actually works versus what’s hype. The engineers who skip the hands-on step lose the judgment they need to evaluate AI output effectively. His Substack, Molochinations, named after Scott Alexander’s essay “Meditations on Moloch,” explores these themes through a systems-thinking lens.
Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters
Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Philip Su
Philip Su is a Distinguished Engineer (IC9) who scaled Facebook’s London office from a dozen engineers to 500+, served as site lead at OpenAI, and now builds Superphonic — an AI-powered podcast player. He writes about the future of software work at Molochinations on Substack. LinkedIn
You can link with Philip Su on LinkedIn.
