Why Waiting for the Next AI Model Can Pay Off - John Stecher, Blackstone & Scott Worland, Norm AI

20:453분 읽기AI Engineer2026. 11. 05.컴퓨터/소프트웨어 · 경영/리더십 · AI/미래기술

핵심 요약

Strategic timing of AI adoption combined with robust data management and rapid prototyping allows organizations to replace obsolete software systems efficiently as model capabilities scale.

하이라이트

  • A solid data strategy moving information out of transactional systems into accessible formats remains essential for successful AI agent deployment.

  • Engineers can leverage AI agents to automate tedious software development tasks like writing functional test cases and versioning libraries.

  • Comprehensive evaluation samples and hand-labeled test sets are critical to measure system health and maintain consistency in highly regulated industries.

  • Modern development harnesses enable teams to transition rapidly from concept and planning to workable proof-of-concept software.

  • Rapidly declining software production costs allow internal applications to be built for specific short-term purposes and discarded when obsolete.

타임라인

  1. Data Strategy and Software Development Velocity

    Expanded context windows since early last year enable systems to process significantly more information and generate greater value. Organizations must move data out of transactional systems so agents can easily access and recall it. Furthermore, automating routine software engineering tasks such as functional and performance test cases significantly accelerates delivery velocity.

    • Cohesive data management is required to prevent AI agents from failing.
    • AI agents offload intellectual cycles by automating software development tasks like test case creation.
    • Straight-through processing combined with injected intelligence replaces rote human decision-making workflows.
  2. Rigorous Evaluations and Architectural Resets

    Early attempts to integrate language models into production required heavy upfront structural scaffolding and workflow sequencing. As native agentic capabilities emerged, teams realized that a large portion of their custom codebases had become obsolete. Maintaining strict evaluation scorecards ensures that model updates or harness changes do not introduce output skew or compromise accuracy in regulated sectors.

    • Extensive human-labeled evaluation sets ensure output accuracy and consistency.
    • Agentic approaches render extensive traditional scaffolding and custom code obsolete.
    • High accuracy standards in financial services demand stringent validation metrics.
  3. Balancing Compute ROI and the Bitter Lesson

    Historical patterns demonstrate that statistical and compute-driven models eventually surpass handcrafted expert systems, echoing the principle that manual rules are frequently replaced by scale. Leaders continuously evaluate the balance between development costs and anticipated business value, sometimes choosing to delay projects until upcoming model iterations reduce implementation costs. Rapid prototyping allows teams to test concepts quickly without over-investing in premature infrastructure.

    • Compute scaling consistently outperforms handcrafted expert rule systems over time.
    • Evaluating return on investment helps determine whether to build an application today or wait for more sophisticated models.
    • Generalizable AI agents can spin up computers and execute complex tasks outside traditional knowledge work.
  4. Production Challenges and the Economics of Software Rewrites

    Transitioning proof-of-concept models into enterprise production environments involves navigating complex cybersecurity constraints and ensuring traceable code monitoring. While teams maintain strict human ownership over core primitives to protect sensitive data, the drastically reduced cost of writing software allows organizations to discard internal applications when newer solutions offer superior business value.

    • Deploying AI tools into enterprise infrastructure requires rigorous cybersecurity and SRE monitoring.
    • Core primitives demand complete human oversight to maintain strict data security.
    • Lower software production costs make frequent application rewrites economically viable.

설명

Blackstone CTO John Stecher and Norm AI CTO Scott Worland discuss building technology that holds up as models keep improving. John explains why a solid data strategy and straight-through processing come before agents, how he weighs ROI against waiting for a better model, and why internal apps can now be thrown away and rebuilt. Scott describes how Norm's large hand-labeled eval set showed that much of its carefully built workflow code was in the way, why the team rebuilt its platform, and how it decides where to invest heavily versus lightly as the frontier moves. Chapters: 0:00 Intro 1:05 Getting AI agents right 1:32 Data strategy comes first 2:21 Straight-through processing still matters 3:46 Norm's early workflow approach 5:05 When agents made the code obsolete 6:42 Evals in financial services 7:40 The bitter lesson 8:54 ROI, and when to wait for the next model 10:25 Getting to a proof of concept fast 12:43 Updating on Claude Code 14:49 The hard part: getting to production 15:45 Parts that still need human review 17:24 Rebuild instead of maintaining 19:13 Closing thoughts John Stecher https://www.blackstone.com Scott Worland https://www.norm.ai Join us in SF for the second annual AIE CODE summit: https://aie.codes our last flagship summit of 2026. Applications live now!

이 영상에 대해 글쓰기