Six months into the agentic AI explosion, the industry is hitting its first financial and operational walls. The flat-fee subscription model, which powered early adoption, is collapsing under the weight of autonomous workflows. Power users on $200 monthly plans were burning $10,000 in compute, a subsidy Nathaniel Whittemore notes became unsustainable. The result is a rapid shift to per-token billing, with GitHub, Google, and Anthropic all imposing usage limits.
“The economic unit of AI has officially moved from the person to the token.”
- Nathaniel Whittemore, The AI Daily Brief
This economic shift coincides with a radical change in what it means to be a software engineer. The craft's traditional moat - the friction of specialized syntax - is gone. As Naval argues, models now understand “fuzzy, sloppy English,” rendering manual implementation a legacy skill. Engineer Max Hodak hasn't written a line of code in months but is building more than ever, simply brute-forcing problems by throwing multiple AI models at them iteratively.
The new bottleneck isn't typing, but thinking. Dax Raad, co-founder of OpenCode, warns that while AI makes shipping trivial, it turbocharges bad decisions, leading to Frankenstein products impossible to maintain. The most valuable engineers now combine “pre-AI principles and post-AI speed.” Their role is shifting to that of an architect: making high-stakes choices about system design and curating reusable blocks of infrastructure in what Guillermo Rauch calls a “block economy.”
“The human role is now ‘completing the model’ through architectural decisions... it still requires a human to decide between Postgres or Clickhouse.”
- Guillermo Rauch, Naval
The friction has moved from code to compute. GPU supply is the new throttle, bottlenecking even high-growth startups. Elon Musk’s pivot - providing SpaceX’s Colossus data centers to power Anthropic’s Claude - underscores the scramble for infrastructure. As labs like OpenAI and Anthropic launch enterprise consulting arms to bridge a massive “capabilities overhang,” the engineer's job is no longer to write the code, but to judge the output and steer the system that writes it.



