What happens when code costs almost nothing?
Software does not become free. The expensive parts move to specification, integration, trust and maintenance.
Cheaper code increases the amount of software the world attempts to own. That creates new demand for understanding systems, maintaining them and deciding which complexity is worth carrying.
The shift
The surface-level story is speed: more output, shorter cycles, lower production cost. The structural story is that the location of scarcity moves. Once an old constraint becomes cheap, the system reorganises around what is still difficult to obtain—context, judgement, authority, attention or trust.
That distinction matters because markets routinely overvalue the newly abundant thing during a transition. Capability is visible. Integration is quiet. Yet integration is where a possibility becomes a repeated behaviour and, eventually, an institution.
Where the leverage moves
Implementation cost falls, but ambiguity remains expensive. Teams that can specify the right behaviour and verify it in context gain more than teams that simply produce more files.
The practical response is not to chase every new capability. It is to identify which part of the value chain now moves faster, which part becomes newly defensible, and what kind of product can make that shift legible to a user. A good product is a theory of the new constraint made concrete.
The model to hold: capability diffuses; situated judgement compounds.
What I’m watching
A flood of disposable applications will make durable software feel different: legible, supported, coherent and safe to depend on.
The most useful signals will not always arrive as announcements. They appear in changed pricing units, shrinking interfaces, new permission patterns and teams achieving outcomes that their organisational shape should not permit. Those are the moments when the future stops being a claim and starts becoming an operating fact.