Companies are systematically replacing software developers with autonomous AI agents, and the transition is deeper than automating simple tasks. At Block, the change was structural: 14-person feature teams were replaced by squads of one to six people, and developers are no longer writing code by hand.
“We’re not writing code by hand anymore,” said Block executive Owen Jennings on The a16z Show. “That’s over.” Instead, humans manage what Jennings describes as a background fleet of 10 or 20 agents. The company’s internal Builder Bot autonomously writes, tests, and merges code, often completing 85-90% of a feature before a human editor reviews the final 10%.
Owen Jennings, The a16z Show:
- There's been this correlation between the number of folks at a company and the output from the company for decades and decades.
- I think that basically broke.
This shift demands a new kind of operational skill, not just better models. Nathaniel Whittemore reported on The AI Daily Brief that most organizations are flying blind, spending 93% of their AI budgets on infrastructure while allocating a mere 7% to training the people who must now work with these systems. The result is a massive capability overhang where AI’s potential is trapped by human bottlenecks.
The future of work lies in programming agents, not applications. Nufar Gazit explained that the building blocks are becoming portable ‘skills’ - markdown folders with instructions and scripts that agents can execute across 44 different tools. These skills, which have a half-life of about one month, are replacing static internal wikis and becoming the new organizational infrastructure.
Nufar Gazit, The AI Daily Brief:
- Skills are basically folders that contain instructions, scripts, and resources that give AI tools and agents actionable playbooks.
- They are human readable, there is no proprietary format, and you can just take them between tools.
Independently, individuals are mirroring this corporate shift. Shubham Sabu runs a team of six AI agents on a Mac Mini, treating them like a startup staff with shared memory and weekly self-reviews. This move from prompt engineering to workforce management underscores the scale of the change. The role of the software engineer is evolving from builder to context-manager for autonomous systems.
The transition leaves a stark readiness gap. While forward-thinking companies like Block are already restructuring, Whittemore’s data shows eight out of ten enterprise functions scored poorly on data maturity, and most departments are significantly behind on the ‘people’ pillar. The companies that survive won’t be those with the most engineers, but those who can turn their unique data and processes into agentic workflows.


