Boris Cherny works at Anthropic. He literally built Claude Code. he sat down and walked through his actual workflow, and it’s kind of nuts
Here’s the part that hit me hardest:
Most people use Claude Code like a fancy autocomplete. Boris uses it like he’s managing a whole team of employees.
That right there is the difference between people building cool little projects and people building stuff that actually makes money.
A few things he does that I’m stealing:
He runs like 10 Claudes at once. Not one at a time. He’s got terminals open, browser tabs open, even sessions running on his phone. He’s not waiting on Claude. Claude is waiting on him. Wild reframe.
He never lets Claude code first. He plans first. Always. Talks through the whole approach with Claude before a single line gets written. Then he hits go and Claude usually nails it on the first try. The biggest reason builds go sideways? Letting Claude run wild before you’ve actually agreed on what you’re building.
He keeps a “memory file” for Claude. Anytime Claude messes something up, instead of fixing it 50 times, he just writes down the rule once. Now Claude remembers. Genius and obvious at the same time.
If he does something twice, it becomes a shortcut. Same prompt twice? Turn it into a command. Boom, never type it again.
The whole vibe of his setup is less “I’m using AI” and more “I’m running a small company of AI workers.”
That’s the shift. And honestly, it’s the same shift I’m trying to make in my own builds.
Watch the full 30-min workshop here (worth every second, especially if you’re newer to this stuff):