The fundamentals didn't change. The ratio did.
Do the fundamentals still matter? We have the tools now. They plan. They write. They test. They ship. So do we still need to understand the code? Do we even need to read it?
We have been here before. Punch cards gave way to assembly, then to high-level languages, then to frameworks and the cloud. Every new abstraction made building software easier, and every one of them gave us more software, not less. The house is still a house. The carpenter is still a carpenter.
Writing code was never the whole job. It was always the smallest part. Requirements, design, testing, review, deployment, security, and communication were always there too. When writing code gets cheap, the bottleneck moves to deciding what to build, specifying it, reviewing it, and running it.
That is where the fundamentals come back in. You can't review what you can't read. The skill AI erodes first is debugging. So you still need to learn this. Write it once yourself, then hand it off. Know one level of abstraction below the one you use. Let tests, not diagrams or specs, be the gate.
Writing code is now cheap. Owning code is still expensive. Owning code is the craft, and the craft isn't going away.
The fundamentals didn't change. The ratio did. Writing code is now cheap. Owning code is still expensive.
We have leveraged new abstractions before, from punch cards to high-level languages. Every one of them gave us more software, not less.
Writing code was always the smallest part of the job. The role expanded. It did not disappear.
When writing code gets cheap, the bottleneck moves to deciding, specifying, reviewing, and running.
Scope, stakes, and scale decide how much scrutiny code needs. Same tools, different stakes.
You can't review what you can't read. The skill AI erodes first is debugging.
The reps rule: write it once yourself, then hand it off. Know one level of abstraction below the one you use.
Done means it has a test, the tests pass, you saw it work, and you said what you checked and what you didn't.
You are responsible for your career. No one can do it for you, and you can't stop learning.
The slides from the keynote, plus a few places to keep going:
The keynote is the short version. The book covers the fundamentals in depth, and our full-day workshop puts them into practice.