Too many think their job is writing code.
Coding is mostly translation.
You start with (usually) messy human input - a half-baked product idea, a vague ticket, a frustrated customer complaint, a Jira ticket that just says "can we make this faster?"
Then someone has to turn that into something a computer understands.
For decades that translation required a human glued to a keyboard. Syntax mattered. One missing character and the whole build failed.
What happens now that AI is very good at that exact task?
Give it a clear description and it can generate solid code. Not perfect. Not production-ready. But the translation from intent to code happens fast.
Which forces a realization many engineers have yet to fully realize:
Typing computer code was never where the real value lived.
It was never about who could write a for-loop fastest or memorize the most APIs.
The real engineering work happens somewhere else entirely.
Everything else is syntax.
And syntax is exactly what machines are getting very good at.
This is why strong engineers shouldn't fear AI. If anything, it clarifies the profession.
For years the industry rewarded people for how quickly they could translate ideas into code. Now that translation layer is being automated.
What remains is the part that was always the real job.
In other words, the job is finally shifting back to what engineering was supposed to be about.
Not syntax.
Impact.
The engineers who embrace AI will move dramatically faster - exploring more designs, testing more ideas, and eliminating huge amounts of tedious work.
The ones still measuring their value in lines of code are about to discover something uncomfortable.
Engineering isn't.
In the era of AI, it is time to get back to your engineering roots.