AI makes software cheaper. Systems thinking becomes more valuable.
Models make code cheap to write. They don’t make systems cheap to own, and that gap is where the valuable work moves.
- Topic
- Software
- Reading
- 2 min
Writing code is getting cheap fast. A function that took an afternoon now takes a prompt and a review. A prototype that took a week can exist by lunch.
It’s tempting to conclude that software itself is getting cheap. I don’t think it is. One part of it is getting cheap, the part where a clear intention turns into working lines. Most of the cost was never there.
Code was never the bottleneck
Most of the cost of software comes after the first commit. Someone has to keep it running, change it without breaking something three layers away, explain it to the next person and decide what not to build. None of that got cheaper this year.
Cheap code makes it worse. When a feature costs little to produce, you get more features and more integrations, and somebody has to own every one of them.
What becomes valuable
When output is cheap, judgement is scarce. In practice that looks like:
- Knowing where the boundaries are. Which parts of a system should know about each other, and which never should. A model will happily wire everything to everything.
- Choosing what to leave out. Code that was never written needs no maintenance.
- Seeing second-order effects. A change to how money moves, or how data is stored, shows up in places nobody is watching.
- Writing things down. Models work better with clear constraints, and so do teams. Good specs used to be a courtesy. Now they multiply everyone’s output.
None of these skills are new. The effort of typing used to hide them.
The work changed
I spend less time producing code and more time deciding what the code should be, reviewing what was produced and designing the system it lands in. The job looks more like editing than writing.
That makes the reviewer the bottleneck, which is uncomfortable. A model can produce a thousand plausible lines in a minute, and plausible isn’t the same as correct. So I lean on tests, types and small steps I can undo. They make fast change safe.
Open questions
- If juniors learn by writing the code a model now writes, where does the next generation of systems thinkers come from?
- How much review is enough when the volume of changes keeps growing?
- Which of today’s “best practices” were really workarounds for expensive code, and can quietly go?