I often have a thought when I see developers these days.
Problem-solving is done very quickly with AI.
But they are not interested in what happened before.
Why was it made this way,
What was the business context,
They don't ask or try to listen to why the existing code is in this form.
Even not only code written by others,
I was quite surprised to see them applying code they created with AI without properly looking at it.
In one of the projects I experienced,
There were cases where very inefficient and illogical code was included due to business requests.
That was not a result of the developer's skill, but of the situation and requirements at the time.
It was code like a "field artifact" that accumulated history.
But these days, the attempt to understand such context is disappearing.
"Existing code is strange → Rewrite it with AI"
This formula is repeated too easily.
The problem is that the newly written code,
The moment it breaks the existing business logic or operational flow comes more often than expected.
AI helps with implementation.
But it doesn't tell you why it became that way.
What is becoming more important for developers now
is not coding speed or
Aren't they the same thing?
As for how to use AI, honestly, you can just ask the AI.
However
It doesn't substitute for the ability to understand existing content.
Future developers
Will it be more important
to "understand well" rather than "how quickly you can code"?
