Wirth's law is Niklaus Wirth's variant of the Jevons paradox: Software is getting slower more rapidly than hardware is getting faster.
There's no reason for software to be slow anymore
The other day, I saw a viral tweet saying that people talking about how LLMs are causing slow, bloated, code are going to eat crow once they re-write everything in super-optimized assembly. We're not quite at the point where we want to write everything in assembly, but some variant of what Nolan Lawson said about testing, you can choose how many bugs you want now, which I less eloquently noted here, is becoming more true for performance.
🐌 Slow Software for a Burning World 🔥
In a world of “move fast and break things,” we’ve chosen a different tempo — one rooted in care, deep listening, and collective stewardship. Slow software means building for long-term resilience and meaningful participation, rather than chasing novelty, speed, or scale.
Speed Comparison - Programming Languages
Benchmarks run on GitHub Actions. Results may vary based on runner hardware.
Software Acceleration and Desynchronization
A look at the ever-present drive to make software delivery faster and how it might break down various activity loops in organizations.
Jevons paradox
The Jevons paradox or Jevons effect is an economic phenomenon said to occur when technological improvements that increase the efficiency of a resource's use lead to a rise, rather than a fall, in total consumption of that resource. Greater efficiency reduces the amount of the resource needed per application, lowering its effective cost; if demand is sufficiently price elastic, this induces demand, frequently resulting in a net increase of total resource consumption.
Jevons paradox
In economics, the Jevons paradox, or Jevons effect, is said to occur when technological improvements that increase the efficiency of a resource's use lead to a rise, rather than a fall, in total consumption of that resource. Greater efficiency reduces the amount of the resource needed per application, lowering its effective cost; if demand is sufficiently price elastic, this induces demand, frequently resulting in a net increase of total resource consumption.
Slow down to speed up: so much has changed in 6 months’ time
An overview of what’s changed in engineering during the last six months, how various tech companies are changing how they work, and why slowing down could be a sensible strategy
The Jevons Paradox of AI - Wesley's notes
Why AI can make us more productive but will never save us time
Code Is Cheap Now. Software Isn’t.
The barrier to entry for building software has collapsed. The barrier to building something that matters hasn’t moved an inch.
Smarter Operating Systems Will Use Wasm - The Coming OS Revolution by Jonas Kruckenberg @ Wasm I/O
Not just development, distribution of software may change as well - <antirez>
Understanding is the new bottleneck
Agents can write code faster than we can absorb it. Here's why it still matters for humans to understand what they build — and some techniques for doing that efficiently: explainer docs, quizzes, micro-worlds, and shared spaces.
Understanding is the new bottleneck
Agents can write code faster than we can absorb it. Here's why it still matters for humans to understand what they build — and some techniques for doing that efficiently: explainer docs, quizzes, micro-worlds, and shared spaces.
AI & Alignment Raw coding speed isn't the bottleneck. Alignment is the bottleneck. That seems to be a zeitgeist-y theme lately. If you're using AI to code, maybe you're feeling it. You can code more and faster. And clearly a boatload of other developers are doing that too. But software doesn't…
AI & Alignment
chriscoyier.net