Agentic Engineering · Vibe Code Blueprint

Agentic Engineering

Andrej Karpathy spoke at AI Ascent this past week.

He described something he called agentic engineering.

The human stays in the loop. The agent writes detailed documentation. You oversee the architecture. The agent handles the code specifics.

I've been teaching exactly that for almost a year.

Here's what I built it around:

Before any code gets written, you run four phases. Brainstorming. Product requirements. Technical architecture. Then implementation — story by story, with the AI reading your planning documents before it builds anything.

Why? Because without a plan, every feature is built in isolation. The AI has no memory of decisions made in previous sessions. Each prompt starts from scratch.

The documentation is the memory. The human is the director.

Karpathy's framing yesterday was exact: vibecoding raises the floor. Agentic engineering maintains the ceiling — the professional standards, the security model, the architectural coherence that vibe coding can't talk about.

He said you can outsource your thinking. You cannot outsource your understanding.

That's the line I've been trying to write for a year.

I built BMAD and the Vibe Code Blueprint around that principle before it had a name.

Now it does.

Agentic engineering.

The methodology was always the missing piece.

And now you can learn it too.

0 comments