🚀 New Video: How the Creator of Claude Code Actually Uses Claude Code
Most people use Claude Code completely wrong. The defaults teach you to type into one chat, hit enter, wait, type again. That's the loop. The guy who actually built Claude Code does basically the opposite. Boris Cherny runs ~15 Claude Code sessions at the same time, barely types most of his prompts, and dispatches work like a team lead. I read every public post he's made and put the whole thing on one page. The 7 moves: 1. Parallel sessions — 5 in terminal + 5–10 in browser. One session, one job. Opus + thinking mode for all of them 2. CLAUDE.md — the rules file Claude loads automatically. Every time it gets something wrong, you write the fix in. Compounding engineering — month 3 has 50 rules nobody else has 3. Plan mode — Shift+Tab+Tab. Pour energy into the plan, then auto-accept the implementation 4. Slash commands + sub-agents — .claude/commands/ + .claude/agents/. Boris uses /commit-push-pr, /simplify, /verify, /go dozens of times a day 5. /loop — local background loops up to 3 days. His 4: /babysit, /slack-feedback, /post-merge-sweeper, /pr-pruner 6. /schedule — same idea, runs in the cloud. Laptop can close. GitHub events can trigger it 7. Verification (the #1 tip) — "grill me on these changes", "prove it works", "scrap this and implement the elegant solution" The adoptable system if you're not a developer: 2–3 parallel sessions (not 15) + CLAUDE.md + plan-first discipline + named prompts for anything you do twice + 1 loop during workday + 1 schedule overnight + a verification line on every important task. If you do only ONE thing from the video: add a verification line. The quality jump is immediate. 📎 Full Boris Cherny guide PDF pinned below — every move with the setup steps + the Keep-vs-Skip cuts for non-devs. Comment which move you're copying first 👇 [Watch the video here ▶️]