When AI started writing decent code, I did not feel excitement.
I felt unsettled.
Part of it was personal. I had built a career on being able to untangle complex systems, reason through architectural tradeoffs, and hold messy abstractions in my head until they became clear.
But part of it was practical.
If a model can scaffold refactors, generate tests, reason about edge cases, and produce solid patterns in seconds, then the question becomes unavoidable:
What happens to engineers when parts of their skill set become automated?
That fear is not irrational.
Teams are getting leaner. Productivity expectations are rising. Companies are under pressure to ship more with fewer people. AI is not a novelty anymore. It is embedded into workflows.
The work is changing in real time.
The Misunderstanding About AI
There are two extreme reactions to AI.
One camp believes it will replace human engineers entirely.
The other dismisses it as glorified autocomplete.
Both miss something important.
AI does not think like a human. It does not understand systems in the experiential sense. It does not care about uptime, team velocity, or long-term maintainability.
It predicts patterns.
And prediction at scale can look remarkably competent.
But prediction is not judgment.
That distinction is critical.
The Real Fear: Economics and Value
The anxiety around AI usually blends two concerns.
The first is economic.
Will this reduce demand for engineers?
The second is personal.
Will this reduce the value of what I bring?
AI absolutely compresses certain types of work. Boilerplate generation, repetitive refactors, scaffolding, and documentation drafts. The cost of iteration is dropping fast.
But that does not eliminate engineering.
It shifts the bottleneck.
When code generation becomes easier, the constraint moves to:
- Architecture decisions
- Systems integration
- Tradeoff analysis
- Failure modeling
- Product alignment
- Accountability
The floor lowers.
The ceiling rises.
Engineers who compete only on raw output will struggle.
Engineers who operate at the level of systems and constraints will gain leverage.
The Turning Point in My Workflow
The shift for me happened when I stopped using AI as a replacement and started using it as a thinking partner.
Instead of asking it to “write this feature,” I began asking it to stress test my ideas.
I would describe a multitenant billing system with evolving discount rules and ask it to critique the domain model. I would have it enumerate failure modes in webhook handling, idempotency guarantees, and concurrency boundaries. I would ask it to propose alternative abstractions and then interrogate them.
Suddenly, it was not competing with me.
It was expanding my cognitive bandwidth.
Instead of spending an hour drafting a single architecture direction, I could explore multiple viable approaches quickly and focus on the harder question:
Which one survives contact with reality?
My job became less about producing code from scratch and more about defining constraints, filtering options, and owning decisions.
That is higher leverage work.
Reading AI 2041 Put This in Context
While navigating this shift, I started reading AI 2041: Ten Visions for Our Future by Kai-Fu Lee and Chen Qiufan.
The book pairs speculative stories set in 2041 with grounded technical analysis of where AI is realistically heading. It does not frame AI as magic. It frames it as infrastructure.
In one story, AI assistants optimise daily decisions so effectively that they begin shaping behaviour itself. In another, hyper-realistic synthetic media challenges society’s ability to distinguish truth from fabrication. Other chapters explore personalised AI education, autonomous systems, and algorithmic governance.
The consistent pattern is this:
AI expands capability.
Humans remain accountable.
The systems amplify us. They do not originate purpose.
That mirrors what I see in engineering. AI can generate options. It cannot decide what is aligned with the product vision, the business model, or long-term technical health.
Those decisions remain human.
The AI Stack I’m Using
This shift is not abstract. It is operational.
Here are the tools currently shaping how I work.
GitHub Copilot Pro+
GitHub Copilot Pro+ lives directly in my editor. It handles low-level friction extremely well. Boilerplate, repetitive patterns, test scaffolding, and interface implementations. It uses local context to generate code that aligns with the file and project structure.
The fundamental benefit is cognitive offloading.
Instead of spending working memory on syntactic repetition, I stay focused on architecture and intent. Copilot accelerates expression. It does not replace direction.
Variant
Variant is closer to an AI-native website design tool than a coding assistant. Conceptually, it sits nearer to design platforms like Figma make or emerging AI-enhanced layout builders.
Instead of focusing on implementation details, Variant accelerates layout generation, design system consistency, and structured UI exploration.
For engineers who touch frontend systems, this matters.
It shortens the loop between concept and visual artefact. Instead of manually iterating on layout structures or styling hierarchies, AI can generate structured starting points that you refine.
This shifts attention from pixel pushing to experience reasoning.
ChatGPT Codex
ChatGPT Codex is where I go for higher-level reasoning.
When I need to explore design tradeoffs, simulate adversarial critiques, or prototype alternative abstractions, this is the thinking layer.
I use it to:
- Stress test system boundaries
- Model edge case behaviour
- Generate multiple architecture directions quickly
- Challenge assumptions before implementation
The fundamental benefit is parallel cognition.
It feels less like delegation and more like expanding thought capacity. I remain accountable. But I am no longer thinking alone.
The Real Difference Between Humans and AI
AI responds to framed problems.
Humans decide which problems matter.
AI can expand the solution space. It can generate variations at scale. It can surface blind spots.
It cannot choose meaning.
It cannot care about consequences.
It cannot take responsibility when systems fail.
Engineering is not just code generation.
It is ownership.
That part is not automated.
Where This Is Headed
AI will continue compressing certain tasks.
Entry-level work will change. Expectations for productivity will rise. Teams will likely stay leaner.
But the demand for people who can define systems, reason about complexity, and own outcomes is not disappearing.
If anything, it becomes more valuable.
The engineers who thrive will not be the fastest typists.
They will be the ones who:
- Define the right problems
- Set clear constraints
- Interrogate AI outputs critically
- Integrate tools into disciplined workflows
- Take responsibility for results
AI is not replacing engineers entirely.
It is reshaping engineering.
The work becomes less about proving you can produce code alone and more about orchestrating intelligence effectively.
That is not a downgrade.
It is a shift in leverage.
And the sooner we adapt to that reality, the better positioned we will be in the decade ahead.
Top comments (0)