AI Can Write the Code. Can It Run the System? | Grepr CEO Jad Naous

What It Covers

a16z General Partner Martin Casado and Grepr CEO Jad Naous examine how AI transforms software engineering, from Naous's 10-person team shipping in days what once took months, to the harder unsolved frontier of AI-driven operations. They debate whether production systems—with unpredictable workloads and near-infinite failure states—can ever be managed the way code is generated.

Key Questions Answered

• •AI coding leverage is asymmetric by engineer quality: Strong engineers extract disproportionately more value from AI tools than average engineers. At Grepr, the gap between good and mediocre engineers widened by roughly 10x after AI adoption. The reason: AI cannot handle architectural complexity independently—engineers must decompose problems, assign tasks, and validate outputs. Architectural thinking remains the irreplaceable human contribution that determines how much leverage AI actually delivers.
• •Multi-agent workflow with persistent CLI sessions: Naous runs three to four Claude Code sessions simultaneously using Opus, instructing agents to spawn command-line sub-agents rather than Fable sub-agents. CLI sub-agents maintain persistent sessions, preserving context across long tasks. A designated "tech lead" agent reviews pull requests from implementation agents, iterating on a shared design document before any code is written—reducing rework and keeping complex distributed system logic coherent across parallel workstreams.
• •Production infrastructure work compressed from six months to ten days: Naous built Grepr's auto-promotion and data shredding feature—converting semi-structured log fields into independently filterable Parquet/Iceberg columns across a distributed data lake—alone in roughly ten days. The same work would previously require a single engineer approximately six months. The workflow starts with a reviewed PRD and design document before any implementation begins, treating upfront architectural clarity as the prerequisite for effective AI-assisted execution.
• •AI-driven operations requires anomaly detection feeding into reasoning agents, not root-cause backtracking: Most AI SRE systems fail because they start from a lagging indicator—a spiked metric or fired alert—and attempt to backtrack to root cause across complex distributed state. Grepr's approach inverts this: a clustering model scans petabytes of logs daily, surfaces novel patterns never seen before, and passes those signals to an LLM that generates causal hypotheses and verifies which fit observed data, reducing false negatives on real incidents.
• •Observability spend follows diminishing reliability returns as architectures scale: Engineering leaders Naous surveyed in 2023 spent five to twenty percent of infrastructure budgets on observability as a reliability proxy. As microservice architectures expanded telemetry volume faster than functional output, marginal reliability per additional observability dollar flattened. Grepr's model intercepts the data stream upstream, filters signal from noise in real time, reduces downstream observability costs by up to ninety percent, and routes extracted signals to AI reliability layers rather than storing raw telemetry.
• •AI solution quality correlates with whether training distribution matches deployment distribution: Casado frames AI capability through one lens: models perform reliably when the distribution of possible solutions matches the distribution of training data. Code generation works because all code ever written is the training set. Operations fails this test—production failure states are heavy-tailed, exception-driven, and adversarially influenced in security contexts. Self-driving consumed $170 billion over twenty years to achieve worse unit economics than Uber, illustrating the cost of bridging this distribution gap in physical domains.