Boris Cherny, creator of Claude Code at Anthropic. IC4 → IC8 at Meta, now building agentic coding tools.
tldr
- •"latent demand > forcing new behaviors" - steer existing intent, don't create new habits
- •build for future models (Claude Code was built 6 months ahead of model capabilities)
- •50-90% of code at Anthropic now written by AI; ~70% productivity gain per engineer
- •engineering is shifting to orchestrating AI fleets - less deep focus, more context-switching
- •imposter syndrome is normal at every level; no one fully knows what they're doing
- •delegate what you enjoy and know well (Andy Grove) - easier to monitor effectively
career at meta
- •started underleveled (IC4) → gave space to explore, built momentum through strong early impact
- •key projects: Chats and Groups (guerrilla UXR like cafeteria testing), Comet JS rewrite, Public Groups
- •promoted IC4 → IC5 → IC6 → IC7 → IC8 via high-impact work and "better engineering" initiatives
- •side projects built skills + network: Undux state manager, TypeScript book/meetup, 20-40 tech talks
- •moved to Instagram Tokyo → rebuilt credibility bottoms-up (coded heavily due to timezone)
generalist mindset
- •engineers should do product/design/research, not just code
- •automate toil for leverage; build for shared problems
- •latent demand principle: Marketplace emerged from existing buy/sell group posts
leadership insights
- •cross-org work: align on shared goals/hypotheses; cultural mismatches kill projects
- •scoping large work: time-box (30 min-2 hrs), straw-man proposals, design competitions (blue/green teams)
- •no titles at Meta/Anthropic: forces constant re-earning of influence
anthropic & claude code
- •motivated by ChatGPT's "magic"; views LLMs as transformative "alien life" needing safe nurturing
- •chose Anthropic for mission/safety focus (delayed releases, heavy alignment compute)
- •Claude Code started as internal experiment; built for future models (per manager Ben)
- •early versions weak; exploded with Opus/Sonnet 4 (March 2025)
- •usage: pairing/planning mode preferred over pure "vibe coding" (prototypes only)
- •orchestrates 5-15 parallel Claudes via terminal/browser/mobile
- •beyond coding: data scientists for SQL, sales for Salesforce
advice
- •build side quests/20% ideas for growth and leverage
- •think in types (Scala/FP influence); recommends "Functional Programming in Scala"
- •no CS degree? no issue - learn practically on the job
- •use common sense; ignore misaligned big-company processes; trust instincts