The Hybrid Developer: AI + Understanding
The Hybrid Developer: AI + Understanding
From vibecoding to agentic engineering — the model that works
Karpathy's Own Evolution
Remember Karpathy — the man who coined 'vibecoding'? Just one year later, in February 2026, he declared it obsolete:
“Vibe coding is now passe. You are not writing the code directly 99% of the time. You are orchestrating agents who do, and acting as oversight. Engineering — to emphasize that there is an art and science and expertise to it.”
— Andrej Karpathy, February 2026
He now advocates agentic engineering — using AI agents to write code while maintaining structured human oversight. The key difference from vibecoding: you still understand and review what's being built.
The Spectrum of AI-Assisted Development
| Approach | Code Review | Understanding | Best For |
|---|---|---|---|
| Pure Vibecoding | None | None | Throwaway prototypes |
| Assisted Coding | Partial | Good | Daily development |
| Vibe Engineering | Full + Tests | Deep | Production code |
| Agentic Engineering | Oversight | Architectural | Complex systems |
Simon Willison's 'Vibe Engineering'
Django co-creator Simon Willison coined 'vibe engineering' in October 2025 — combining LLM speed with automated testing, planning, documentation, and code review. The human remains the accountable decision-maker.
Your Practical Framework
When to Vibecode (Low Stakes)
When to Engineer (High Stakes)
The Hybrid Workflow
Use AI for First Draft
Let AI generate boilerplate, scaffolding, and initial implementations. This is where AI saves the most time.
Review Every Line
Read the generated code. Understand what it does. Check for security issues, unnecessary complexity, and logical errors.
Test Meaningfully
Don't just run it — write tests that verify edge cases and failure modes. AI writes tests that pass, you write tests that matter.
Refactor for Clarity
Simplify AI's over-engineered output. Remove unnecessary abstractions. Make it readable for the next person.
Own the Architecture
You decide the structure. AI fills in the details. Never let the AI make architectural decisions — that's your job.
Course Conclusion
Vibecoding isn't wrong — it's incomplete. It's a starting point, not a destination. The developers who thrive in the AI era aren't the ones who type the most code or the ones who type the best prompts. They're the ones who understand deeply enough to leverage AI as a force multiplier while maintaining the judgment, security awareness, and architectural thinking that no AI can provide. Build real skills. Use AI tools. Understand your code. That's the path forward.
There are no comments for now.