From Wizards to Wordsmiths: the emotional impact of AI on software professionals
The following is an AI generated summary of the video
From Wizards to Wordsmiths: Rethinking Software Identity in the Age of AI
Like many software professionals, I've had a complicated emotional reaction to AI.
Not because I doubt its usefulness.
Quite the opposite.
The problem is that it's often too useful.
When the Hard Part Disappears
Recently, I was working on a game project I'd spent hundreds of hours building.
I had reached a problem involving depth scaling and rendering calculations. It wasn't an area I was particularly strong in, and after struggling through tutorials and experiments, I eventually asked an AI assistant for help.
It generated a better solution almost instantly.
The strange thing is that I didn't feel relieved.
I felt disappointed.
Even saddened.
A problem I'd wrestled with for days simply evaporated.
What had once felt like a challenge suddenly felt trivial.
And with that, some of my enthusiasm disappeared too.
The John Henry Problem
The feeling reminded me of the folk story of John Henry.
John Henry famously raced a machine, won, and then collapsed from exhaustion.
The story is often told as a celebration of human determination.
But underneath it lies something sadder.
A skill that once defined a person's value becomes obsolete.
Many software professionals are experiencing a version of that feeling today.
We've spent decades developing skills that felt specialised and valuable.
Then suddenly a machine performs parts of that work faster than we can.
Even when it helps us, it can still feel like a loss.
The Wizard Identity
For a long time, many of us unconsciously thought of ourselves as technical wizards.
We knew obscure commands.
We understood complex systems.
We could solve problems that seemed mysterious to everyone else.
There was a certain identity wrapped up in that.
Software engineering often felt like mastering a collection of arcane spells and secret knowledge.
The better you became, the more valuable that expertise appeared.
AI challenges that self-image.
Not because expertise no longer matters, but because some of the magic has become accessible to everyone.
The Magic Hasn't Gone Away
It's tempting to conclude that AI eliminates the need for expertise.
It doesn't.
Anyone who has worked seriously with large language models knows they make mistakes.
They hallucinate.
They misunderstand context.
They confidently produce incorrect answers.
In many ways, they're like a colleague who has read millions of books but occasionally says something completely absurd.
Expertise still matters.
Someone has to evaluate the output.
Someone has to recognise when the answer is wrong.
Someone has to understand the problem well enough to ask the right questions.
The role hasn't disappeared.
But it is changing.
The Rise of the Wordsmith
The shift I find most helpful is moving from thinking of ourselves as wizards to thinking of ourselves as wordsmiths.
The value increasingly lies in our ability to:
- Define problems clearly.
- Express intent precisely.
- Ask better questions.
- Communicate effectively.
- Evaluate solutions critically.
In other words, language becomes more important than ever.
The better we can articulate what we want, the better results we get from both AI systems and human collaborators.
Language Shapes Thought
This matters because language isn't simply a tool for expressing ideas.
It helps create them.
Writing often forces us to organise thoughts that previously existed only as vague intuitions.
Many difficult problems become clearer the moment we attempt to describe them precisely.
That's why writing can feel almost magical.
Not because it creates solutions.
Because it reveals them.
The process of turning chaotic thoughts into structured language often exposes assumptions, contradictions, and opportunities that were previously hidden.
The New Role of the Engineer
Several shifts seem to be emerging in AI-assisted development:
From Producer to Manager
Instead of writing every line of code ourselves, we increasingly direct systems that generate code on our behalf.
From Implementation to Intent
The focus moves from describing how something should work to describing what outcome we want.
From Delivery to Discovery
Trying multiple solutions becomes dramatically cheaper, allowing rapid experimentation.
From Content to Knowledge
Understanding the problem becomes more valuable than producing the implementation.
These shifts don't remove the need for engineers.
They simply change where engineers create value.
Writing Code Was Never the Bottleneck
One insight that keeps resurfacing is that software development was never primarily about typing.
The hard part has always been understanding.
Understanding the problem.
Understanding the users.
Understanding the trade-offs.
Understanding whether a solution is actually correct.
The cost of generating code is falling rapidly.
The cost of understanding, testing, and trusting that code remains high.
Perhaps higher than ever.
Expanding Our Professional Identity
The danger comes when we define ourselves too narrowly.
If "coder" is the entirety of our professional identity, AI feels threatening because it directly affects that identity.
A healthier model might look something like this:
- Problem solver
- Communicator
- Collaborator
- Researcher
- Reviewer
- Engineer
- Coder
Coding remains important.
It's just one part of a larger professional toolkit.
Most software problems aren't purely technical anyway.
Many are communication problems.
Process problems.
Organisational problems.
Relationship problems.
The ability to navigate those challenges has always mattered.
AI simply makes that more obvious.
Final Thoughts
I remain unsettled by the pace of change.
Many engineers do.
But resisting the technology won't stop it.
The challenge is learning how to integrate these tools without allowing them to dismantle our sense of purpose.
The solution, I think, is remembering that we were never valuable solely because we could type code.
We were valuable because we could understand problems, reason about systems, communicate ideas, and create solutions.
Those skills remain.
The tools are changing.
The profession is evolving.
The wizard may be fading.
But the wordsmith is becoming more important than ever.