The Future of Software Development - Vibe Coding, Prompt Engineering & AI Assistants
Summary
AI is not merely another application wave: the panel treats models as a fourth infrastructure pillar because they change chips, data centers, latency requirements, and the programming model itself. Martin Casado’s dividing line is that applications have “abdicated logic”—rather than programmers encoding every decision, software asks the model to “come up with the answer for me.” For career software people, “software is being disrupted” and starting to eat itself.
The supercycle thesis is that cheaper capabilities expand the TAM, create new users and behaviors, and leave incumbents poorly equipped for the resulting white space. The panel’s blunt investor heuristic is that “infra creates TAM”; dismissing a developer tool because today’s market looks small risks missing another GitHub. Natural language also delivers the low-code promise by making programming accessible to anyone with domain knowledge and an idea.
Developer distribution is becoming consumer-like just as the technical audience grows from the low tens of millions to above 50 million. Individual developers increasingly discover and adopt tools bottom-up, while companies still evaluate them through centralized technical buying centers. The panel therefore emphasizes understanding both individual adoption and enterprise buying centers.
The panel has moved away from its early thesis that AI offered “no defensibility anywhere in the stack.” In today’s expansion phase, zero-sum thinking is “deadly”: chips, clouds, models, and applications can all grow simultaneously, while deep engineering, distribution, embedded integration logic, and high switching costs preserve value. Consolidation may eventually produce oligopolies or monopolies, but infrastructure layers rarely disappear.
The panel highlights a shift from prompt engineering to context engineering: model performance depends on selecting the right data, tools, priorities, and guarantees before each call. That creates potential infrastructure around data pipelines, indexes, prioritization, and formal guarantees. The panel expects a new software formalism to emerge over roughly five years, not a world where natural-language wishes eliminate systems engineering.
Agents work best where their loops contain objective error correction, which is why coding is ahead of general web automation. Code can be linted, interpreted, compiled, and tested, arresting error propagation; a vaguely instructed agent sent to “wander out in the woods and bring back a bear” still breaks down. Martin has nevertheless become a convert for bite-sized, well-articulated coding tasks.
Better coding tools are more likely to create more developers and software than to collapse engineering employment. Programming remains creative specification, while customers buy software because someone encoded the correct workflow and domain decisions—not because CRUD applications are inherently difficult to type. The median pull request reportedly changes only two lines, underscoring that understanding the need is often harder than implementing it.
Deep dive
Not yet available upstream; scheduled sync will retry.