Boris Cherny is the creator of Claude Code. In the short video above, he shows something much bigger than a few new coding features.
He shows how the way we work with AI is starting to change.
Instead of opening Claude, writing one prompt, waiting for the answer, and repeating the process, Boris is moving toward routines.
Claude can work on several tasks at the same time. It can write code, open the result, test it, notice something is wrong, fix the problem, and test again. Other routines can watch a pull request, repair failed tests, respond to review comments, and keep the work moving while the developer is doing something else.
Boris explains it in one very useful line:
“I’m not the one doing the prompting. I’m the one creating a routine that does the prompting.”
That is the idea worth learning.
The future of Claude Code is not simply better prompts. It is learning how to give Claude a job, the right context and tools, and then a way to check its own work before calling the job finished.
If you are new to Claude, Claude Code, agents, or AI coding, think of this post as a small learning course. Start with the video above. Then follow these three guides in order. You can begin from the basics and slowly move toward the workflows Boris is demonstrating.
1. Start with how Boris actually works
This is the best next step after the video. It goes deeper into Boris’s own working method: CLAUDE.md, parallel agents, verification, automated reviews, loops, long-running work, and even managing Claude Code from his phone.
How Claude Code’s Creator Boris Cherny Actually Uses It
Boris Cherny created Claude Code, the system now changing how developers explore repositories, write features, fix bugs, review pull requests, run tests, and manage entire coding workflows. Then he pushed it further. He stopped writing code by hand. He stopped opening his IDE. Eventually, he even moved beyond prompting Claude one task at a time.
2. Then learn how to build the system yourself
This takes the same ideas and turns them into a practical setup. It covers project context, model choice, Skills, MCPs, plugins, subagents, loops, graph workflows, prompts, commands, and verification.
Claude Code After Generation 5 Models: The Master Guide
Claude Code changed twice in the same month.
3. Finally, understand the models behind all of this
Here we go wider: Sonnet 5, Opus 5, and Fable 5, what each model is good at, how much control to give it, how to choose effort levels, and how to combine models, tools, agents, and verification into a complete working system.
You do not need to learn everything at once.
Watch Boris build. Understand how he thinks. Then use the guides to rebuild that way of working step by step.
By the end, Claude Code should make much more sense, not simply as an AI that writes code, but as a system you can teach to work, check, fix, and keep going.
Video credit: Anthropic
Source: Watch the original Anthropic video on YouTube
