This is a fuller English adaptation of the Korean article on agentic engineering after vibe coding. The source uses Andrej Karpathy’s discussion as a starting point, but its main focus is practical: when anyone can generate code with AI, real engineering shifts toward specification, verification, environment design, and responsibility.
Original Korean article: 에이전틱 엔지니어링: 안드레이 카파시가 말한 바이브 코딩 이후의 개발 방식
Why Agentic Engineering Has Become Important
A turning point after late 2025
The article argues that AI coding entered a new phase as models became capable of longer, tool-using work. Vibe coding showed that natural language can produce working prototypes. But when prototypes move into production, teams need more than vibes. They need a way to assign tasks to agents, constrain them, test outputs, and recover from mistakes.
Agentic engineering names this emerging discipline. It is not just writing prompts. It is designing the full loop in which an AI agent receives a goal, uses tools, modifies artifacts, checks results, and reports its reasoning for human review.
What Software 3.0 Means
Code is not only in files
Software 1.0 was explicit code written by humans. Software 2.0 often referred to learned weights and data-driven behavior. Software 3.0, as discussed in the source, includes prompts, tool interfaces, workflows, evaluations, context, and agents as part of the software system. The product is no longer only a repository of files.
This changes what engineers must version, review, and test. A prompt template, an evaluation dataset, an agent routine, or an MCP tool schema can be as important as a function in a codebase. If these pieces are invisible, the system cannot be operated reliably.
Vibe Coding Lets Anyone Build, but Real Work Is Different
What the MenuGen example shows
The Korean article mentions the kind of example where a non-specialist can create an app or interface quickly with AI. This is the promise of vibe coding: describe the feeling, iterate visually, and get a working result. It expands who can make software.
However, production work still involves edge cases, data integrity, security, accessibility, performance, maintenance, and user support. Vibe coding is excellent for exploration, but the moment a product affects customers or business operations, engineering discipline returns.
What humans still must own
Humans remain responsible for goals, ethics, tradeoffs, and accountability. An agent can implement a feature, but it does not own the consequences of a privacy breach, a bad medical recommendation, or a financial error. The source article emphasizes that the human role rises toward judgment rather than disappearing.
Agentic Engineering Is the Skill of Specification and Verification
The core practice is writing specifications that agents can execute and humans can verify. A good specification includes context, expected behavior, constraints, examples, non-goals, test commands, and acceptance criteria. It should also define what the agent must not change.
Verification is equally important. Teams need unit tests, integration tests, golden examples, simulations, benchmark tasks, human review gates, and rollback plans. The question is not whether the AI produced something impressive. The question is whether the team can prove the result is correct enough for the intended use.
Verifiable Environments Are the Core Product Opportunity
What founders should watch
The article identifies a business opportunity: environments where AI agents can safely perform work and be evaluated. In coding, this may mean sandboxes with tests. In design, it may mean versioned assets and approval flows. In enterprise operations, it may mean permissioned data connectors and audit logs.
Founders should look for workflows where the output can be checked. If a task has clear evaluation signals, agents can improve quickly. If the task is vague, subjective, or legally sensitive, human review must remain central.
Where AI-Native Developer Differences Come From
Productivity is not typing speed
The difference between developers will not be who types fastest. It will be who decomposes problems better, gives agents the right tools, reads output critically, and builds reusable workflows. A strong AI-native developer can run several streams of work while maintaining quality gates.
Agent-First Infrastructure Is Needed
Human UI and agent interfaces are different
Many current tools are designed for human clicks. Agents need structured APIs, logs, machine-readable state, reversible actions, and narrow permissions. Agent-first infrastructure does not mean removing humans; it means making work legible to both humans and machines.
Conclusion: Developers Do Not Disappear; Their Role Moves Up
The source article’s conclusion is optimistic but disciplined. AI expands who can create software, but reliable software still requires engineering. Agentic engineering is the next layer: designing environments where AI agents can work productively while humans retain responsibility for direction and verification.
Related Reading
FAQ
How is agentic engineering different from vibe coding?
Vibe coding focuses on generating software through natural language iteration. Agentic engineering adds specifications, tools, tests, permissions, and verification loops.
Does Software 3.0 replace coding?
No. It expands software to include prompts, agents, context, data, and evaluation alongside traditional code.
What should developers prepare?
They should practice task decomposition, specification writing, automated testing, review systems, and safe tool design for agents.
