Team Lead & Fullstack Developer at QuickBlox. 20+ years building software, 20 years teaching it. Exploring how AI changes the way we write, review, and understand code.
The evolution from vibe coding to agentic engineering is real — Karpathy himself illustrated it. He coined "vibe coding" in February 2025, then declared it outdated and introduced "agentic engineering" a year later, and ultimately hand-coded his Nanochat project because agents "didn't work well enough at all." The trajectory is telling: generation speed isn't the bottleneck. Understanding is. In our experiments (25-40% gains with rigorous review), the biggest insight was that AI excels as an analysis tool — understanding unfamiliar code, comparing branches — more reliably than as a code generator. When you mention "orchestrating agents," do you see the orchestrator's primary job as directing generation, or as maintaining understanding of what agents produce?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The evolution from vibe coding to agentic engineering is real — Karpathy himself illustrated it. He coined "vibe coding" in February 2025, then declared it outdated and introduced "agentic engineering" a year later, and ultimately hand-coded his Nanochat project because agents "didn't work well enough at all." The trajectory is telling: generation speed isn't the bottleneck. Understanding is. In our experiments (25-40% gains with rigorous review), the biggest insight was that AI excels as an analysis tool — understanding unfamiliar code, comparing branches — more reliably than as a code generator. When you mention "orchestrating agents," do you see the orchestrator's primary job as directing generation, or as maintaining understanding of what agents produce?