Why Devs Using Claude Are Outpacing Their Teams
Boris Cherny sees individual output jumping while companies lag on workflows
@bchernyTL;DR:
- Engineers are getting a lot more done with Claude on their own
- Teams haven't updated processes, reviews or security yet
- Early movers on AI dev practices might build real leads
What's happening
Boris Cherny keeps hearing the same story. Individual engineers are shipping way more using Claude, but their teams and companies haven't changed how they work.
The pattern
He sees this as a repeating four-step cycle in AI adoption and points to a Claude artifact that maps it out.
The real bottleneck
Gains are showing up first with single developers. The holdup now is getting processes, code reviews, security rules, and team structures to catch up. For tools like Claude it's less about model power and more about how organizations handle change. Companies that sort out AI-assisted workflows early could pull ahead, while others risk messy tools and oversight gaps. This also pushes Claude deeper into normal dev work as agents become standard infrastructure.
Quick take
Medium significance for industry trends, developer tools, and market impact.