Every time programming tools get better, someone announces the death of “real programming.”
It happened with IDEs.
It happened with StackOverflow.
Now it’s AI.
The underlying assumption never really changes.
That programming is mostly about typing code.
The Long History of Reducing Typing
The software industry has been trying to reduce the amount of typing involved in programming for a very long time.
Early programming involved punch cards and assembly code. Every instruction explicit. Every step manual. If you wanted a computer to add two numbers, you carefully described how the processor should do it.
Punch Cards
It worked. It was also miserable.
So people started inventing ways to avoid doing that.
High-level languages appeared so developers didn’t have to think in raw machine instructions. Compilers translated human-readable code into something the computer could actually execute. Libraries meant you didn’t have to re-implement the same basic functionality every week.
Later we added IDEs with autocomplete and syntax highlighting. Package managers so dependencies didn’t require archaeology. StackOverflow so people didn’t have to memorize the entire internet.
Each step removed a little more friction.
Each step reduced the amount of typing involved in getting something done.
Now AI can generate code and explain language quirks on demand.
Which, historically speaking, is exactly the direction programming tools have been moving for decades.
And before anyone gets nostalgic about the “proper way” of doing things, it’s worth remembering what the proper way once looked like: Punch cards
Nobody is seriously campaigning to bring those back.
The Panic Is Always the Same
Every wave of better tools comes with the same warning.
Compilers would ruin programming.
IDEs would ruin programming.
StackOverflow would ruin programming.
Compilers would ruin programming.
IDEs would ruin programming.
StackOverflow would ruin programming.
Now it’s AI.
Apparently this time the prediction will finally come true.
Quiet interesting considering code generation is hardly a new concept.
What Programming Actually Is
So what is programming then?
Despite appearances, it was never mainly about typing code.
Code is just the way we describe solutions to a machine.
The actual work happens before that.
Programming is about:
- understanding a problem
- breaking it into smaller parts
- deciding how those parts interact
- managing complexity so the system still makes sense a year later
The typing comes last.
That’s the implementation step.
Which is also the step tools have been trying to simplify for decades.
Good developers were never valuable because they could type faster.
They were valuable because they could figure out what needed to be built in the first place.
And because they could look at a messy system and still understand what was going on.
That skill has a name: Abstraction
Taking something complicated and finding the structure that makes it manageable.
Sometimes that structure becomes an algorithm.
Sometimes a system architecture.
Sometimes just a well-chosen interface.
Sometimes realising you have seen that problem in another context before.
Code is the artifact that comes out of that thinking.
Which is why tools that reduce the amount of typing don’t remove programming.
They remove the mechanical part of it.
If anything, that makes the real skill easier to see.
When a tool can generate the syntax, what remains is the part that actually matters:
- defining the problem
- evaluating possible solutions
- understanding the tradeoffs
- recognizing when something will break later
AI can help explore solutions.
It can generate variations, suggest approaches, and explain patterns.
But someone still has to decide whether the solution makes sense in the real system.
And that part was never about typing.
Programming isn’t disappearing
The tools are just getting better at the boring parts.
Which means the part that actually requires thinking becomes harder to ignore.
If typing code was the job, autocomplete would have replaced us years ago.
The people most worried about AI replacing developers tend to assume that typing was the job. Which might explain some of the anxiety. Fortunately, that was never the job.