In late 2025 coding agents crossed a line: they started doing what you asked, almost every time. This lesson defines agentic engineering, separates it from vibe coding, and shows what you still own when code becomes cheap.
Key takeaways
- Vibe coding means not looking at the code. It's fine when the only person a bug can hurt is you.
- Agentic engineering means agents write and run the code while you keep the professional quality bar.
- Code is cheap now. Good code isn't. The skill is turning cheap code into good software.
- You still own what's worth building, the design, the proof that it works, and your understanding of the system.
- Agents don't make you faster automatically. In a 2025 trial, experienced developers were 19% slower while believing they were faster.
Try it with your agent
Open a real project in Claude Code, Codex or Cursor and paste this:
I'm learning agentic engineering. Explore this repository and suggest three small, low-risk tasks you could complete end to end. For each one, tell me how you would prove it works (a test, a command, a screenshot). Don't change any files yet.
Transcript
Intro
In February 2025, Andrej Karpathy gave a name to a new way of programming. A year later, he said it was already out of date. This lesson is about what replaced it.
Vibe coding
He called it vibe coding. You fully give in to the vibes, embrace exponentials, and forget that the code even exists. It was perfect for weekend projects. It was not how you'd build a bank.
What changed
Here's the short history. Autocomplete finished your lines. Chat assistants wrote snippets you pasted in. Vibe coding let the model drive. Then, in late 2025, coding agents crossed a line. As Simon Willison put it, they now almost always do what you told them to do.
Karpathy described his own workflow flipping in a single month. In December, he went from writing about eighty percent of his code himself to delegating about eighty percent of it to agents.
Boris Cherny, who created Claude Code, says agents now write one hundred percent of his code. He ships dozens of pull requests a day, without editing a single line by hand.
Two disciplines
But vibe coding didn't simply grow up. A different discipline appeared next to it. Vibe coding means you don't read the code, which is fine when the only person a bug can hurt is you. Agentic engineering means agents write and run the code, while you keep the professional quality bar.
Karpathy's own definition: agentic engineering is about preserving the quality bar of what existed before in professional software. You go faster, but you're not allowed to ship a vulnerability just because an agent wrote it.
The name
The name has two halves. Agentic, because most of the time you're no longer typing the code. You orchestrate agents and act as oversight. And engineering, because there's an art, a science and real expertise to it. It's a skill you can learn and get better at.
Code is cheap
This changes what's scarce. As OpenAI's Ryan Lopopolo puts it, implementation is no longer the scarce resource. Simon Willison asks the real question: if I can churn out ten thousand lines in the time it used to take me to write a hundred, how do I make that code good?
What you own
That question is what this course answers, and it starts with what doesn't change. You still own what's worth building, the design and the taste, the proof that it works, and your understanding of the system. As Karpathy says, you can outsource your thinking, but you can't outsource your understanding.
Reality check
Now a reality check. In a 2025 trial, experienced open source developers expected AI to make them twenty-four percent faster. They were actually nineteen percent slower, and still believed they'd been sped up. Tools have improved a lot since then, but the lesson stands. Agents don't make you faster automatically. Skill does.
The autonomy slider
Karpathy calls this the autonomy slider. At one end, you type and the AI suggests. At the other, agents work for hours on their own. You are in charge of the slider. Agentic engineering is choosing the right setting for each task, and making the higher settings safe.
Course map
Here's the path. First, how agents actually work. Then the core workflow with a single agent. Then your toolkit: memory files, tools and skills. Then scaling up to many agents at once. Then quality, safety and teams. And finally, the engineer you become.
Quick check
Quick check. Which of these is agentic engineering? Tap your answer.
Try it
Try this with your own agent. Ask it to find three small, low-risk tasks in a real project, each with a way to prove it worked. Don't let it change anything yet. You'll use these tasks throughout the course.
Recap
Let's recap. Vibe coding forgets the code exists. Agentic engineering keeps the quality bar while agents do the typing. Code is cheap now, good code isn't. And you still own the judgment. Next, let's open the hood and see how a coding agent actually works.