LangChain
AI-assisted summary of The Future of AI Agents with Andrew Ng | Interrupt 26 — original source. Check the original for full context.
Source published:
Key ideas
- Coding agents are accelerating software engineering by 10x to 100x, shifting organizational bottlenecks downstream to product scoping, marketing communication, and legal compliance. (2:01)
- Enterprise bottom-up AI adoption has created point solutions with minor efficiency gains; meaningful transformation requires top-down workflow redesigns focused on uncapped revenue growth rather than cost savings. (13:29)
- Forward deployed engineers and proprietary platforms risk severe vendor lock-in, prompting Andrew Ng to advise limiting software commitments to one-year contracts to preserve technical optionality. (23:33)
- Enterprises face impending multi-million-dollar data overhauls as historical data warehouses built for structured tables fail to deliver fragmented unstructured documents to autonomous agents. (26:38)
Detailed notes
## Background Published by LangChain on YouTube on June 17, 2026, this video features a fireside chat between Andrew Ng and LangChain founder Harrison Chase at the Interrupt 26 conference. According to the page description, the session covers how rapidly coding agents are reshaping engineering teams, the emergence of the product management bottleneck, the contrast between incremental wins and genuine enterprise transformation, and the looming overhaul required for enterprise data architectures.
## TL;DR Andrew Ng explains how coding agents have accelerated raw software development by 10x to 100x, pushing organizational bottlenecks downstream into product scoping, marketing, and legal compliance. He argues that enterprises must move beyond bottom-up point solutions focused on minor labor cost savings and instead make strategic, top-down bets designed to fuel business growth. Ng also emphasizes the importance of preserving optionality by avoiding multi-year vendor lock-in, defending open-weight models, and investing in vendor-neutral infrastructure. Finally, he outlines a massive upcoming wave of enterprise data re-architecture needed to transition legacy relational data systems into agent-ready unstructured data pipelines.
## Atmosphere & style The session carries a warm, collegial, and highly pragmatic tone, shaped by the established partnership and easy banter between Harrison Chase and Andrew Ng. Ng's delivery is measured and grounded, balancing genuine enthusiasm for agentic tooling with clear-eyed skepticism toward AI doomsaying narratives and vendor hype. It feels like an intimate, battle-tested masterclass for practitioners, blending practical developer insights—like using smartphone IDEs and schema-on-read databases—with high-level executive strategy.
## Bulletin - [02:01](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=121s) Coding agents are accelerating software engineering by 10x to 100x, shifting organizational bottlenecks downstream to product scoping, marketing communication, and legal compliance. - [13:29](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=809s) Enterprise bottom-up AI adoption has created point solutions with minor efficiency gains; meaningful transformation requires top-down workflow redesigns focused on uncapped revenue growth rather than cost savings. - [23:33](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1413s) Forward deployed engineers and proprietary platforms risk severe vendor lock-in, prompting Andrew Ng to advise limiting software commitments to one-year contracts to preserve technical optionality. - [26:38](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1598s) Enterprises face impending multi-million-dollar data overhauls as historical data warehouses built for structured tables fail to deliver fragmented unstructured documents to autonomous agents.
## Key takeaways - [00:39](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=39s) AI doom narratives and warnings of an imminent job apocalypse have gained excessive traction and remain largely unfounded. - [01:06](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=66s) The rapid evolution of coding agents like Claude Code, OpenAI Codex, and Gemini CLI has transformed daily workflows, enabling engineers to direct code generation from mobile phones and dedicated local hardware. - [02:01](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=121s) Exponential gains in coding velocity have exposed severe bottlenecks in upstream product management and downstream marketing and legal sign-offs. - [02:01](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=121s) Engineering teams are reorganizing into lean pods of 1 to 10 empowered generalists who handle cross-functional tasks like drafting marketing copy and legal terms using frontier models. - [06:02](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=362s) Software developers gain exponential leverage through a LEGO brick approach—combining traditional and AI-native building blocks rather than hand-crafting low-level code. - [08:34](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=514s) Tools like Context Hub overcome model training cutoffs by injecting up-to-date documentation and SDK specifications directly into coding agent prompts. - [10:24](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=624s) Educational platforms like LearnDream.ai are pioneering interactive learning experiences that replace canned lecture videos with interruptible conversational avatars and live JavaScript demos. - [13:29](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=809s) Automating isolated steps in existing workflows yields only marginal labor savings; true enterprise ROI requires top-down workflow redesigns, such as transforming multi-week loan underwriting into a 10-minute automated approval. - [16:44](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1004s) Enterprises should target top-line business growth rather than cost cutting because headcount savings have a hard ceiling while revenue expansion is virtually unlimited. - [18:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1107s) Pursuing 20% to 50% transformative growth targets is often more effective than chasing 2% marginal gains, as ambitious goals force organizations to invent creative new business models. - [21:07](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1267s) Plummeting agentic prototyping costs enable teams to explore dozens of low-cost ideas before executive leadership commits capital to a focused portfolio of strategic bets. - [22:00](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1320s) Forward deployed engineers accelerate enterprise deployments, but long-term enterprise staffing will tilt predominantly toward internal AI talent rather than external vendor personnel. - [23:33](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1413s) Enterprises should refuse multi-year vendor contracts and 20% to 30% discounts to avoid locking their infrastructure into foundation models that could be eclipsed within a year. - [25:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1527s) Open-weight models consistently trail frontier proprietary releases by only six to nine months, serving as vital infrastructure for production workloads and counteracting vendor lock-in. - [26:38](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1598s) Corporate data architectures require massive re-engineering because existing data warehouses were designed for structured tables rather than retrieving unstructured PDFs, audio, and video for agents. - [29:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1767s) Using schema-on-read NoSQL databases like MongoDB significantly accelerates agentic prototyping by eliminating the risk of catastrophic schema migration failures caused by LLMs.
## Detailed walkthrough ### [00:14](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=14s) Welcome Back to Interrupt and Reflections on AI Hype
Harrison Chase opens the fireside chat by welcoming Andrew Ng back for year two of Interrupt, LangChain’s agent conference. Harrison notes that Andrew’s session from the inaugural year was the most viewed and most liked talk on YouTube from the event, eliciting applause from the audience. Setting the stage for the discussion, Harrison asks Andrew what over the past year has moved faster than expected in the AI landscape, and what has moved slower.
Andrew responds that on the slower or less rational side, the hype has exceeded his expectations, and doomsaying narratives have gained far more traction than he would have guessed. In particular, he explicitly pushes back against the fear of an imminent labor collapse: “And then also the doomsaying narratives also got more traction, unfortunately, that would have guessed, including the job apocalypse, which I don't think is going to be a thing.”
[01:06](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=66s) The Rapid Evolution of Coding Agents
On the positive side, Andrew observes that coding agents have advanced at a pace that surprised even him. While he acknowledges that the broader industry trope—that everything in AI fundamentally changes every three months—is mostly hype, that rapid pace actually rings true for agentic code generation. The frontier of capabilities and competition is moving so quickly that Andrew’s own daily toolchain shifts continuously. Half a year ago, his workflow was dominated almost exclusively by Anthropic’s Claude Code. Today, while he still relies heavily on Claude Code, he increasingly incorporates OpenAI Codex, Google's Gemini CLI, and open-source alternatives like OpenCode.
These emerging workflows have also altered the physical context of programming. Andrew shares that he never anticipated spending so much time coding directly from his smartphone, often driving tasks on dedicated hardware: “I wouldn't have guessed a year ago that I'd be coding so much on my phone as well. So these workflows, like many of you have a Mac Mini in my office. So all these workflows changing really rapidly.” Beyond software engineering, agentic patterns and workflows are steadily penetrating enterprise environments.
[02:01](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=121s) The Product Management Bottleneck and Shifting Organizational Constraints
When Harrison asks what the future of software engineering looks like, Andrew revisits a concept he introduced a year prior: the product management bottleneck. The core premise is that when implementation speed increases exponentially, the constraint immediately migrates to scoping the problem, gathering user feedback, and deciding what to build. Over the past year, this bottleneck has intensified—in a healthy way—because writing software has accelerated by 10x to 100x. However, engineering speed has now accelerated so much that virtually every other organizational function is struggling to keep pace.
```mermaid flowchart LR accTitle: The Shifting Organizational Bottleneck accDescr: Acceleration in software development pushes constraints downstream to PM, marketing, and legal.
subgraph Dev["Core Development"] A["Coding Agents & Tooling"] -->|"10x–100x speedup"| B["Software Shipped in 1 Day"] end
subgraph Bottlenecks["Downstream Bottlenecks"] B --> C["Product Management<br>(Scoping & Customer Needs)"] B --> D["Marketing<br>(Communicating Rapid Features)"] B --> E["Legal & Compliance<br>(Sign-offs & Terms of Service)"] end ```
Andrew explains that his teams are now actively bumping into marketing bottlenecks, where product features ship faster than marketers can digest and articulate them to users. Similarly, legal compliance has become an acute friction point: waiting a week for legal sign-off was acceptable when a feature took three months to write, but when code is drafted in an afternoon, a week-long legal review stalls the entire pipeline. Because of this, Andrew sees engineering teams restructuring into small pods of one to ten people made up of empowered generalists:
> “So I think a lot about how software engineering teams in the future will be organized, and I don't think I know the answer. But increasingly, I find myself setting up very small parts, you know, anywhere from one to 10 engineers in a team, of often generalist, high context, highly empowered generalists, that are given a set of very wide guardrails within which they can just run like crazy and build in ship code, and even drive decisions like writing, marketing, copy that are traditionally outside the purview of engineering.”
By the pigeonhole principle, if a cross-functional initiative requires engineering, scoping, terms of service, design, and marketing copy, a lean two-person squad must wear multiple hats. Andrew jokes about his own marketing skills, noting that while AI does not make him a great marketer, it makes him “slightly less bad.” In practice, engineers are now using frontier models to draft initial terms of service before handing them off to lawyers for final polish, cutting development cycles dramatically.
[04:50](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=290s) The Backgrounds of Frontier Generalist Engineers
Harrison asks about the typical pedigree of these high-velocity generalists—specifically whether they are seasoned software engineers expanding their scope or professionals from product, marketing, and operations who are picking up coding for the first time.
Andrew explains that while successful contributors can emerge from any background, the vast majority of people thriving in these hybrid roles began with deep technical and software engineering foundations:
> “I think it's actually possible for people of any background to learn to do a lot of this. But the largest number of bodies doing this well right now seems to be people that came from an engineering background.”
Engineers possess a natural advantage in understanding the mechanics and edge cases of frontier AI tools. However, Andrew highlights that he has also watched product managers learn to code effectively, marketers build working software prototypes, and operations personnel assemble end-to-end internal tools. The overarching requirement is not just deep domain training, but the willingness to step into unfamiliar disciplines with an AI assistant at one's side.
[06:02](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=362s) Combinatorial Software Development and the LEGO Brick Mental Model
Andrew offers a framework for how developers should think about modern software engineering: mastering modular building blocks. The ecosystem is inundated with both AI-native components (retrieval-augmented generation, agent frameworks, evaluation frameworks, guardrails) and traditional infrastructure building blocks (UI kits, authentication systems, frontend and backend persistence layers, databases).
Because the open-source community and proprietary API providers are producing new blocks at an unprecedented rate, developers who understand what each block does can achieve exponential leverage:
> “So I find that developers that have a good mastery of enough building blocks can often put them together in combinatorially many ways to very rapidly build software.”
To illustrate this, Andrew uses the analogy of building with LEGOs: - With only a single white brick, what one can construct is severely constrained and uninteresting. - Introducing black, yellow, brown, and green bricks alongside specialized squiggly elements causes the space of possible creations to expand combinatorially and exponentially. - In software, the engineer's primary job is recognizing the functional properties of these disparate blocks, while directing coding agents to handle the tedious assembly work.
[08:34](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=514s) Context Hub: Overcoming Model Knowledge Cutoffs for Tool Use
A central roadblock coding agents encounter when working with newly released building blocks is the model training cutoff. If an API or SDK was published after a model's knowledge cutoff date, the agent has no intrinsic awareness of its existence, parameters, or calling syntax.
To solve this problem, Andrew teamed up with his friend Rohit Prasad to build Context Hub, which functions as a specialized knowledge repository or “Stack Overflow for AI agents.” Context Hub ingests and serves up-to-date documentation and SDK specs directly into coding agent prompts, while also providing a mechanism for agents to submit feedback on doc clarity. Andrew notes that whenever an API has clunky or hard-to-remember syntax, he points his agent at Context Hub to ingest the latest docs and execute the calls autonomously, significantly accelerating his personal coding speed.
Harrison chimes in with an amusing logistical clarification: LangChain also recently shipped an internal project named Context Hub. While the names collide, Harrison points out that Andrew's project is specifically designed to feed up-to-date documentation into coding agents, encouraging the audience to try it out. Harrison also highlights the enduring partnership between LangChain and DeepLearning.AI, noting that LangChain was the second partner (immediately following OpenAI) to launch a short course on the platform, which became a primary discovery channel for early LangChain users.
[09:50](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=590s) The Evolution of AI Education
Harrison turns the conversation toward education, asking how pedagogical practices must adapt to an AI-accelerated world and how those insights are being woven into DeepLearning.AI’s curricula. Andrew emphasizes that the baseline curriculum for technical workers has fundamentally shifted. Software engineers can no longer focus solely on static syntax and traditional algorithms; they must deliberately learn coding agent workflows, stay abreast of proliferating architectural building blocks, and cross-train in adjacent disciplines like product management to operate effectively inside lean, autonomous teams.
[10:24](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=624s) Transforming AI Education: From Static Videos to Interactive Conversations
Andrew Ng shifts the discussion to how education itself is evolving. Beyond simply changing *what* people learn—a need addressed through organizations like DeepLearning.AI and Coursera—the delivery mechanism of training has been ripe for rethinking for a very long time, though Andrew notes it is "actually not quite here yet."
To explore new learning paradigms, his team launched a preview site called LearnDream.ai (referred to in the session as CodeDream.ai). The core thesis is that users should not be forced into a conventional online course format:
> “This is not a course, it's a conversation where the experience you tried to build was for you to come and get on a simulated video call with me...”
In this environment, if a user wants to sit back and passively absorb a presentation on Context Hub and coding agents, the AI avatar will present. However, the learner can interrupt the AI at any moment to ask questions. Andrew also highlights an experiment where standard videos and slides are replaced entirely with live JavaScript. When presenting a demo in this format, learners can click directly into the video window and enter their own prompts or queries in real time. When Harrison Chase clarifies whether this in-video interaction is live today, Andrew confirms it is:
> “That's live. So imagine if instead of me screen sharing in a video, I am, you know, JavaScript sharing in a video and so you can interact with whatever I'm called screen sharing because it's running JavaScript code, not a canned video.”
Despite these experiments, Andrew argues that the grand transformation of education has been somewhat over-hyped. While current online materials are vastly better than a decade ago—pointing to a newly launched course on Transformers by Sharon Zhou featuring rich, interactive visualizations rather than simple lecture recordings—he emphasizes that the truly radical shift in educational formats is still an ongoing effort that he spends significant time thinking about.
---
[13:29](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=809s) Enterprise AI Adoption and the Loan Underwriting Paradigm
Harrison Chase asks how enterprises are currently adopting AI across broader industries, whether it is happening faster or slower than expected, and what models work best. Andrew explains that through AI Aspire, an AI advisory firm he co-founded with his partner Chris Tan, they advise Fortune 50, Fortune 500, and Global 2000 companies on their overall AI strategies. Across these large enterprises, a consistent theme emerges: nearly everyone tried a bottom-up, “let a thousand flowers bloom” strategy, and boards and CEOs are now questioning where the return on investment actually is.
Andrew argues that bottom-up innovation remains valuable for idea generation, but it naturally leads to isolated point solutions that yield minor efficiency improvements rather than end-to-end business transformations. To illustrate, he examines how banks approach loan underwriting, which typically follows five distinct stages:
```mermaid flowchart LR accTitle: Loan Underwriting Workflow Transformation accDescr: A comparison showing point-solution automation of a single step versus end-to-end redesign for a 10-minute loan product.
subgraph PointSolution ["Incremental Point Solution"] direction TB M1["1. Market loan"] --> A1["2. Receive application"] A1 --> R1["3. AI review & approval<br/><i>(Saves ~1 hour human labor)</i>"] R1 --> D1["4. Final diligence"] D1 --> E1["5. Execute loan"] end
subgraph RedesignedFlow ["Top-Down Redesigned Workflow"] direction TB M2["1. Market 'Get approved in 10 minutes'"] --> A2["2. Immediate data routing infra"] A2 --> R2["3. Instant AI credit decision"] R2 --> D2["4. Scaled diligence & execution"] end ```
If an enterprise keeps the traditional weekly turnaround time intact and merely substitutes an AI agent to handle the one hour of human review time, they have captured only an incremental operational saving. A genuinely transformative approach rethinks the entire pipeline to launch a product marketed as "get approved in 10 minutes." Doing so, however, requires executive-level buy-in because marketing, data infrastructure, and diligence operations must all be completely re-architected.
> “Bottom-up innovation often results in point solutions that drive incremental efficiency gains, which are actually a good thing, but not the transmission, not the broader transformation that AI has been promising us and that I think we should work to deliver.”
---
[16:44](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1004s) Cost Savings vs. Driving Business Growth
Andrew encourages companies to steer AI initiatives toward top-line growth rather than limiting themselves to headcount reductions or cost savings. His fundamental rule of thumb is simple:
> “Because we can only save so much money, but growth has almost no practical ceiling. So the more exciting ideas I find usually relate to driving business growth rather than savings.”
When Harrison asks for concrete examples of AI driving business growth, Andrew points out several practical workflows: - **Instant Financial Products:** The aforementioned 10-minute loan approval process that captures market share by out-servicing competitors. - **Customer Support and Contact Centers:** While routinely viewed through the narrow lens of labor cost reduction, augmenting support operations allows an organization to resolve customer issues far faster and at greater volume, turning a support interaction into a brand-differentiating, growth-driving experience. - **Drive-Thru Voice Automation:** Automating restaurant drive-thru ordering pipelines creates a smoother, faster, and more delightful experience that directly drives order throughput and customer retention.
---
[18:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1107s) Measuring ROI: Why Big Bets Beat 2% Incremental Targets
Addressing Harrison's question on how leadership should quantify AI ROI, Andrew acknowledges that because enterprises are so diverse, there is no generic, one-size-fits-all formula. However, he cautions against getting bogged down in marginal accounting exercises over whether an agent provided a 2% lift offset by a 1% implementation cost.
He shares an unintuitive operational insight: chasing transformative gains can often be easier and more motivating than pursuing tiny, incremental targets:
> “Sometimes driving incremental gains is harder than driving transformative gains. Because if you tell someone to improve their business results by 2% next year, then they're like, all right, my boss is telling me to work 2% harder or 5% harder or whatever. But if you try to search your ways to drive 20% business growth or 50% business growth, then you can't just get everyone to work 50% harder in the company and you have to come up with more creative solutions.”
He closes this section by recounting how client companies frequently overwhelm advisors with uncurated backlogs. One major financial institution handed AI Aspire a spreadsheet containing over 300 distinct AI ideas, asking them to pinpoint which ones merited genuine capital expenditure. Andrew notes that identifying the winners is rigorous work: it demands deep technical feasibility analysis paired with exhaustive business evaluation to prune hundreds of surface-level ideas down to a tightly focused handful of high-impact strategic bets.
[21:07](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1267s) Strategic AI Bets and Top-Down Resource Allocation
Harrison Chase brings up high-impact enterprise AI initiatives, noting that the "swing for the fences" projects tend to originate as top-down mandates from leadership. Andrew Ng agrees, explaining that companies should not gamble their entire future on a single reckless bet, but rather construct a carefully considered portfolio of several high-upside initiatives.
```mermaid flowchart TD accTitle: Resource Allocation for AI Projects accDescr: Progression from cheap low-budget agentic prototyping to top-down capital allocation for a portfolio of strategic bets.
subgraph Prototyping ["Bottom-Up Prototyping"] A["Agentic Code Experiments"] --> B["Plummeting Prototyping Costs"] B --> C["High Volume of Small POCs"] end
subgraph Selection ["Portfolio Strategy"] C --> D{"$100K Budget Ceiling"} D -->|"Resource Limits"| E["Select Portfolio of Thoughtful Bets"] end
subgraph Execution ["Top-Down Execution"] E --> F["Executive Resource Allocation"] F --> G["Meaningful Business Impact"] end ```
Ng highlights that agentic coding has dramatically altered early-stage exploration because the cost of prototyping has plummeted, allowing teams to churn through dozens of experimental prototypes with minimal friction. However, prototyping is only the beginning. Teams inevitably run into resource limits on modest budgets, and backing projects with meaningful capital requires executive sponsorship. As Ng puts it: “I find that businesses, hopefully not take one wild swing for the fences, is more a portfolio of a handful of thoughtful bets where if anyone pays off, it will be meaningful for the business.”
[22:00](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1320s) Forward Deployed Engineers: Hype Versus Reality
Harrison turns the conversation to forward deployed engineers (FDEs), a model gaining massive traction across enterprise AI adoption, asking whether every company will eventually employ them and why they carry such outsized influence. Ng acknowledges that Silicon Valley is “definitely having a moment of FDEs” and gives a nod to Aaron Levie’s thoughtful stage remarks on the subject earlier at the conference. While Ng sees the embedded engineering model as an effective mechanism to accelerate deployment, he cautions that public excitement has run slightly ahead of practical operational ratios.
Inside typical enterprises, Ng predicts that the long-term ratio of internal staff to embedded vendor engineers will lean heavily toward in-house AI talent, with only small, focused squads of external FDEs operating on site. Building reliable agentic workflows demands far more than raw coding chops; it requires business acumen, stakeholder management, change management, deep technical judgment, and the courage to push back on technically infeasible customer demands. As Ng observes: “So that's why I like FDEs. I'm excited about the growth. Let's help more people get jobs as FDEs. But I think the hype is also, as is often the case, a bit greater than the actual reality.”
[23:33](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1413s) Vendor Neutrality, Optionality, and Avoiding Multi-Year Lock-In
The core operational tension with embedded FDEs, Ng argues, is the near-impossibility of finding vendor-neutral engineers. When an enterprise brings in FDEs from an external provider, those engineers invariably configure the entire infrastructure around their employer's proprietary model or platform. This creates massive lock-in risks in a market where leadership shifts every few quarters.
Ng emphasizes that because nobody can reliably predict what will be the frontier foundation model or the top coding agent a single year from now, maintaining technical optionality is paramount. Enterprise software vendors frequently attempt to lock clients into multi-year commitments by offering 20% to 30% price breaks, but Ng strongly advises against surrendering agility for small discounts. To retain independence, organizations need vendor-agnostic infrastructure layers like LangSmith for tracing, evals, and observability across any underlying model provider.
> “I personally almost never sign longer than a one-year contract, regardless of the discounts offered, because I value that optionality to work with whatever vendor would be the best in a year's time that I don't know about.” — Andrew Ng
- Frontier model leadership turns over so quickly that predicting next year's best coding agent or LLM is impossible. - Vendors use 20% to 30% contract discounts to lock enterprises into three-year terms. - Vendor-neutral platforms like LangSmith give teams observational visibility without binding their data pipelines to one model ecosystem.
[25:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1527s) The Strategic Imperative of Open-Weight Models
Turning to foundation model ecosystems, Harrison asks about the trajectory of open-source and open-weight models compared to closed frontier APIs. Ng notes that open weights have maintained a remarkably steady performance gap, trailing frontier proprietary releases by approximately six to nine months. Because frontier models carry steep token costs for production volume, Ng's teams rely extensively on open-weight alternatives, deploying them both off-the-shelf and fine-tuned for specialized workflows.
However, Ng voices serious concern about political headwinds threatening open-source AI, citing recent discussions emerging from the White House regarding mandatory pre-release inspections for open models. He notes that he has been in direct contact with administration contacts to push back against policies that could dismantle community-driven AI under the guise of national security or geopolitical rivalries with China. In his assessment: “I feel like if we can all protect open source, open weight, it will make the world much richer, and also help all of us preserve optionality.”
[26:38](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1598s) Rearchitecting the Enterprise for Unstructured Data
Harrison shifts to data strategy, asking what companies must fix before deploying operational agents over enterprise knowledge bases. Ng reveals that through his work at AI Fund and AI Aspire, data architecture is the single most pervasive pain point voiced by corporate leadership. For two decades, enterprises poured hundreds of millions of dollars into relational databases, data warehouses, and structured tables. While structured data remains crucial, modern AI's breakthrough capability is understanding unstructured formats: PDFs, raw text, slide decks, images, audio, and video.
```mermaid flowchart LR accTitle: Structured Versus Unstructured Enterprise Data Evolution accDescr: Historical focus on relational structured data transitioning to agent-ready unstructured data pipelines.
subgraph LegacyEra ["Past 10-20 Years"] direction TB S1["Relational Databases"] S2["Spreadsheets & Tables"] S3["Rigid Human Permissions"] end
subgraph AgenticEra ["Next Multi-Million Dollar Wave"] direction TB U1["PDFs, Text, Images & Audio"] U2["Agent-Centric Governance"] U3["Dynamic Context Delivery"] end
LegacyEra -->|"Exposes Gaps In"| AgenticEra ```
Companies simply do not possess modern architectures capable of delivering the right unstructured context to the right agent at the exact moment it is needed. Ng has audited the vendor landscape and found zero off-the-shelf software solutions that adequately resolve this challenge. Consequently, his teams have resorted to building custom experimental data architectures from scratch. He forecasts that upgrading legacy repositories into "agent-ready" unstructured pipelines will trigger massive corporate spending over the coming years: “I actually foresee that just as many businesses had very large data architecture problems, data architecture kind of work to reorganize the structured data, over the next few years there will be very large, I'm going to say tens of millions, maybe hundreds of millions of dollars types of projects in many businesses to rethink the data architecture to make the data more AI ready or more agent ready.”
When Harrison presses on why current systems fail so miserably, Ng rattles off a catalog of structural roadblocks: - Severe data fragmentation across disconnected local drives, cloud buckets, and legacy storage silos. - Incompatible permission schemes that were authored exclusively for human employees rather than autonomous software agents inheriting user scopes. - Lack of centralized governance, monitoring, and standardized schema definitions for unstructured assets. - Vast graveyards of compliance documents—such as regulatory PDF filings in banking—that were hoarded for 20 years without ever being read or indexed.
[29:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1767s) Prototyping Velocity: Why Schema-on-Read and NoSQL Beat Migrations
Before concluding, Ng shares a practical engineering lesson tailored for the builders in the audience, noting that MongoDB’s leadership was slated to speak next. Although relational databases remain the gold standard for massive, stable production workloads, Ng admits that he heavily favors MongoDB and NoSQL engines whenever he builds and prototypes with AI coding agents.
Relational database migrations introduce immense drag during fast-paced development cycles. While an LLM successfully handles schema alterations most of the time, the rare failure mode can be disastrous: “And we've all had that, one in a hundred times that we asked AI to do a database migration and did something clever like, erase my whole database instead, right?” Schema-on-read architectures completely bypass this danger. By writing unstructured JSON documents directly into a flexible database, engineers avoid tearing down and rebuilding schemas every time an agent generates a new data field. Harrison agrees that autonomous coding agents are fundamentally altering developer tool selection, accelerating iteration speed and rewarding tools that eliminate structural bottlenecks. Harrison thanks Ng for his contributions to the AI community, bringing the fireside chat to a close amidst enthusiastic audience applause.
## Notable quotes > [23:33](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1413s) I personally almost never sign longer than a one-year contract, regardless of the discounts offered, because I value that optionality to work with whatever vendor would be the best in a year's time that I don't know about. — Andrew Ng
> [16:44](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1004s) Because we can only save so much money, but growth has almost no practical ceiling. So the more exciting ideas I find usually relate to driving business growth rather than savings. — Andrew Ng
> [25:27](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=1527s) I feel like if we can all protect open source, open weight, it will make the world much richer, and also help all of us preserve optionality. — Andrew Ng
> [06:02](https://www.youtube.com/watch?v=OaRhpwz_TGM&t=362s) So I find that developers that have a good mastery of enough building blocks can often put them together in combinatorially many ways to very rapidly build software. — Andrew Ng
## Mentioned Andrew Ng, Harrison Chase, LangChain, Interrupt, Claude Code, Anthropic, OpenAI Codex, OpenAI, Gemini CLI, Google, OpenCode, Context Hub, Rohit Prasad, DeepLearning.AI, LearnDream.ai, Coursera, Sharon Zhou, AI Aspire, Chris Tan, Aaron Levie, LangSmith, AI Fund, MongoDB
## Video description Andrew Ng sat down with Harrison Chase for a wide-ranging fireside chat at Interrupt, the agent conference by LangChain.
Watch the full session and get insights on: - How fast coding agents have evolved and how the way small teams ship is being reshaped - The "product management bottleneck" and why accelerating software development just moves the constraint somewhere else - How enterprises are getting incremental AI wins but missing the bigger transformation - The data architecture rework most companies haven't started yet ...and so much more
The Future of AI Agents with Andrew NG | Interrupt 26 0:00 Welcome and intro 0:39 What surprised Andrew most in the past year 1:06 The rise of coding agents 2:01 The product management bottleneck 4:50 What background do these new generalist engineers come from 6:02 How to get into AI software engineering 7:50 Building blocks, LEGO bricks, and combinatorial development 8:34 Context Hub and keeping agents up to date 9:50 DeepLearning.AI, LangChain, and short courses 10:05 How education is changing with AI 11:46 LearnDream.ai and interactive learning 13:29 Enterprise AI adoption: what's working and what isn't 14:46 The loan underwriting example 16:44 Cost savings vs. driving growth 17:11 Good examples of AI driving business growth 18:27 Measuring ROI 19:07 Swinging for the fences vs. incremental gains 22:00 Forward deployed engineers: hype vs. reality 23:01 Vendor lock-in and preserving optionality 25:04 LangSmith as a vendor-neutral layer 25:27 Open source and open-weight models 26:38 Data strategy before building agents 28:17 Unstructured data and the coming rearchitecture 31:22 Closing thoughts
Extra resources: • Everything we shipped at Interrupt: https://www.langchain.com/blog/interrupt-2026-overview • Meet LangSmith Engine: https://www.langchain.com/blog/introducing-langsmith-engine • About LangChain: https://www.langchain.com/
[Source](https://www.youtube.com/watch?v=OaRhpwz_TGM)