Pragmatic Leverage in the AI Software Factory

X postMario ZechnerOpinion

Mario Zechner highlights an analysis by Dex Horthy on achieving true leverage with AI in software engineering. Horthy argues that accelerating code generation alone yields minimal overall gains, as writing code historically represents only 25 to 50 percent of delivery time. Substantial acceleration occurs only when AI aids planning and alignment.

Key points

  1. Writing code accounted for only 25 to 50 percent of feature delivery time even prior to AI; the majority is spent on planning, review, and verification.
  2. Using AI purely for code generation compresses 2–4 hours of typing down to 10–20 minutes without resolving other process bottlenecks.
  3. Real delivery speed increases (2x to 3x) happen when AI is incorporated into initial planning and alignment phases.
  4. Horthy models rework as 'expected pain': the probability of required changes multiplied by how disruptive the fix will be.
  5. A pragmatic 80/20 approach prevents diminishing returns: spending six hours writing a flawless spec is inefficient if ten minutes of planning can remove 80 percent of expected pain.

Why it matters

Development teams frequently adopt AI code assistants expecting massive velocity increases, only to find project delivery times barely change. The primary bottleneck in software projects is clarifying requirements and fixing architectural misalignments rather than keystroke speed. Focusing AI leverage on planning delivers far greater operational benefits.

Analysis

Horthy connects software engineering practices with risk-adjusted leverage. Rather than choosing between zero-context prompts and exhaustive manual specifications, he advocates for pragmatic, multi-phase steering. Developers should alternate between high-level architectural overview and technical implementation details to resolve uncertainty where it matters most, avoiding both unguided agent runs and excessive upfront planning.

Original post

Mario Zechner

@badlogicgames · 29 July 2026

recommended reading, if you don't follow dex you're ngmi. also, please stop posting useful stuff. haven't written a blog post in ages and this makes me feel bad. t.co/wKFoxMkHPT

585 likes9 replies913 bookmarks98.2k views

View on X

Summary generated by AI (Gemini 3.8 Flash, 27 September 2026). It may contain errors – the original source is authoritative.

Similar in content, found by the AI search.

  • X post:Mario Zechner

    Mario Zechner on Modular Codebases vs External Memory and Documentation

    Mario Zechner argues that relying on dedicated memory systems and heavy documentation for code is inefficient. Instead, a clean, modular codebase with small components and a lightweight repository map is all that is required.

    494bookmarks19.6kviews

    AI & LLMs· Opinion

  • X post:Justin Duke

    Software Factories: Why the Value Lies in Org Process, Not Infrastructure

    Justin Duke highlights an essay by Cole Murray exploring the concept of the 'software factory'. Murray, maintainer of the open-source platform OpenInspect, argues that agentic development systems succeed or fail based on organisational processes rather than commoditised tooling.

    1kbookmarks124.8kviews

    AI & LLMs· Opinion

  • Video

    Video:CURT

    Harness Engineering: How to Build a Software Factory with AI Agents

    In his talk at the AI Engineer World's Fair, Tessl's Dru Knox introduces the concept of a software factory, where coding agents produce all user-facing code whilst engineers build and maintain the factory infrastructure. He outlines harness engineering (also referred to as loop engineering) as the guiding discipline, dividing engineering work into inner, outer, and meta loops to improve autonomy, automation, and overall code quality.

    AI & LLMs· Talk

  • X post:cole murray

    Software Factories as a Collaboration Model

    Cole Murray argues that building a 'software factory' is not merely an engineering or tooling exercise, but fundamentally about shaping how teams within a company collaborate.

    2.3kbookmarks77.2kviews

    Web development· Opinion

  • Video

    Video:AI Native Dev

    The Reinvention of the Dev Team in the Agentic AI Era

    At AI Native DevCon, Hannah Foxwell examines how agentic software engineering disrupts traditional team dynamics, organizational ratios, and engineering bottlenecks. As development velocity explodes, the operational friction moves away from writing code toward product validation, continuous safety, and sustainable on-call operations.

    AI & LLMs· Talk

Let's talk about your project

Locations

  • Mattersburg
    Johann Nepomuk Bergerstraße 7/2/14
    7210 Mattersburg, Austria
  • Vienna
    Ungargasse 64-66/3/404
    1030 Wien, Austria

Parts of this content were created with the assistance of AI.