Adam Jacob on AI native infrastructure automation

Changelog Changelog Oct 30, 2025

Audio Brief

Show transcript
This episode explores the evolving landscape of AI development, from changing tech culture around outages to the fundamental re-architecture AI demands and its unique market entry strategies. There are three key takeaways from this discussion. First, the tech community's response to outages has shifted from empathy to harsh criticism, particularly for dominant players like AWS. Second, while AI valuations are high, strong fundamentals rooted in revenue growth differentiate the current AI boom from past speculative bubbles. Third, the true power of AI in software lies not in the models themselves, but in agents orchestrating robust, deterministic systems, signaling a primitive 'DOS era' for AI tools and necessitating top-down market approaches for transformative change. The tech community now exhibits a more brutal and unforgiving stance towards major outages, especially from dominant providers like AWS. This marks a significant cultural shift from the empathetic 'HugOps' movement of the past. Unlike past speculative periods such as the dot-com era, the current AI boom is characterized by strong fundamentals. Public market valuations for AI companies are tied to real revenue growth, rather than pure hype, suggesting a differentiation from prior bubbles. The true power of AI in software development comes from re-architecting systems around AI agents. These agents act as 'glue' for well-defined, deterministic tools, creating a competitive moat in the underlying systems they orchestrate, rather than in the AI models alone. Current AI development tools are still primitive, comparable to the 'DOS era' before a more intuitive 'Windows' phase. Introducing such transformative AI products often requires a top-down go-to-market strategy, as enterprise leaders quickly grasp the 'existential' implications while practitioners may be fatigued by general AI noise. Ultimately, the AI landscape requires both technological innovation and a conscious recalibration of cultural norms and market strategies.

Episode Overview

  • The episode begins by analyzing the tech community's harsh reaction to a recent AWS outage, noting a cultural shift away from the empathetic "HugOps" movement of the past.
  • The conversation then pivots to the AI boom, debating whether it's a financial bubble and concluding that strong fundamentals differentiate it from past hype cycles like the dot-com era.
  • A deep dive into the practical application of AI in software development reveals that its true power lies in re-architecting systems around AI agents, which act as "glue" for deterministic tools.
  • The discussion concludes by framing the current state of AI development as the primitive "DOS era" before a user-friendly "Windows" phase, and explores the unique top-down go-to-market strategies required for such transformative technology.

Key Concepts

  • Shift in Outage Culture: The tech community's response to major outages has moved from empathy ("HugOps") to a more brutal and unforgiving sentiment, particularly when the company is a dominant entity like AWS.
  • The "Not a Bubble" Argument: While private AI market valuations are high, public market valuations are tied to real revenue growth with modest forward multiples, unlike the pure-hype valuations of the dot-com era.
  • The Agent as Glue: The most significant value of AI in software is not the LLM itself, but its role as an orchestrator or "glue" for well-defined, deterministic systems. The competitive moat lies in building the best underlying systems for an AI to use.
  • The "DOS Era" of AI Tooling: Current AI development tools are compared to the early, command-line DOS era—powerful but primitive. The more intuitive, user-friendly "Windows" phase of AI tooling has not yet arrived.
  • Transformative Re-architecture: The true impact of AI is not just using it as a simple tool, but fundamentally re-architecting software around its capabilities, sometimes rendering years of previous development work obsolete.
  • Top-Down Go-to-Market: Selling novel AI products is often more effective with a top-down approach, as enterprise leaders quickly grasp the "existential" implications for their organizations, whereas practitioners are often fatigued by the general "AI noise."
  • Evolving Developer Workflow: The developer's interaction with AI is no longer a single command but an iterative "dance" of prompting, reviewing, and refining. The role is shifting from babysitting an AI to directing it and working in parallel.

Quotes

  • At 1:12 - "It went to brutality... It was like we were playing Mortal Kombat, man, you know?" - Adam Jacob describing the aggressive public reaction to the AWS outage.
  • At 24:20 - "It's not pets.com... It's not Infospace where like, the emperor literally had no clothes except hype, and we hyped ourselves to a market cap bigger than Microsoft. That was a bubble." - Contrasting the solid fundamentals of current AI companies with the hype-driven dot-com bubble companies.
  • At 1:02:13 - "The agent is glue. That's the future... The value is not going to live in the LLM. It's going to live in what are the deterministic systems that we connect to the LLM to help that orchestration do the right thing." - Arguing that the competitive advantage will come from building the best underlying systems for AI to interact with.
  • At 81:59 - "This is DOS 4.2. This is like the worst it's ever going to be. We have no idea what the right interaction models are... we're grubbing around in the dark." - Adam emphasizes how nascent and unrefined the current tooling is, despite its power.
  • At 101:13 - "It's very strange. What do you mean by oh no? Like, the implications are massive organizationally." - Adam details the "existential crisis" that enterprise leaders experience when they realize how this new technology will fundamentally change their operations.

Takeaways

  • The most durable value in the AI era will come from building robust, deterministic systems that AI agents can reliably orchestrate, rather than from the AI models themselves.
  • We are in the earliest stages of AI-native development; today's powerful but clunky tools represent a massive opportunity for innovation in creating more intuitive and effective user experiences.
  • Successfully bringing transformative AI products to market may require a top-down sales strategy that targets leadership's strategic and existential concerns, bypassing practitioner fatigue with AI hype.
  • As systems become more complex, failures are inevitable, and the erosion of empathy within the tech community poses a cultural challenge that needs to be addressed.