We scan new podcasts and send you the top 5 insights daily.
ZenML co-founder Hamza Tahir notes that building durable AI agents—managing non-deterministic code safely and reliably—is essentially a reinvention of core MLOps principles. The fundamental software engineering practices for productionalizing complex, non-deterministic systems are cyclical, moving from DevOps to MLOps and now to AgentOps.
Fully autonomous agents are not yet reliable for complex production use cases because accuracy collapses when chaining multiple probabilistic steps. Zapier's CEO recommends a hybrid "agentic workflow" approach: embed a single, decisive agent within an otherwise deterministic, structured workflow to ensure reliability while still leveraging LLM intelligence.
The core needs of AI agents—version control, testing, observability—mirror those of human developers. However, the sheer scale and speed of agentic workflows mean existing tools like Kubernetes are insufficient, requiring a fundamental reimagining of the entire infrastructure stack.
A new specialized role, "AI Ops," is set to emerge, focusing on the operational management of AI systems. This function will handle GPU management, model orchestration, and agent reliability, filling a critical production gap much like DevOps did for software development a decade ago.
The endgame for software development isn't just code completion, but an "AI factory." A chain of specialized agents will handle design, coding, review, and security. This requires an interoperable platform where different models can check each other's work, with humans as "agent managers."
The new benchmark for engineering maturity is "agentic development." This isn't just auto-complete; it's a full workflow where AI agents write code, open pull requests, and perform reviews overnight, guided by senior engineers who act as mentors to the "smart but inexperienced" AI.
Inspired by fully automated manufacturing, this approach mandates that no human ever writes or reviews code. AI agents handle the entire development lifecycle from spec to deployment, driven by the declining cost of tokens and increasingly capable models.
As marketers deploy autonomous AI agents for content, prospecting, and campaigns, a new 'Agent Ops' function is required. This role monitors performance, catches failures, and onboards new agents, mirroring how DevOps manages software deployment but for the new AI-driven marketing stack.
Many developers believe tweaking prompts and logic ('harness engineering') is the hardest part of building agents. The real bottleneck, however, is scaling, reliability, and managing production infrastructure—a common miscalculation that managed services aim to solve.
The debate isn't between manual coding and blindly trusting AI ("vibe coding"). A new discipline, "agentic engineering," is emerging. This involves creating new best practices, security controls, and governance for using AI agents to build software. This structured approach will replace the current era of unchecked individual developer experimentation.
AI platforms are evolving from simple completion endpoints to stateful, higher-order abstractions like managed agents. This progression is driven by the need to bundle state, tools, and infrastructure, making it easier for developers to achieve optimal outcomes from the model.