With the evolution of generative AI, we have more opportunities to hear that there will be no more work for programmers.
But it's not the profession of programmers that's really starting to change, it's the role.
AIs like GPT-5.6, Claude, and Gemini can now generate code, fix bugs, and create test code. It's not uncommon for implementations that used to take hours to take shape in minutes.
So what do programmers do now? In this article, we will organize the new roles of engineers required in the AI era.
From writing code to designing
Until now, I've spent a lot of time thinking about how to implement it.
But now that AIs can write code, the key is the ability to think about the whole system:
- What to make
- What will the design look like?
- Is there a security issue?
- Is it configured for easy maintenance?
Writing code is becoming a means, not a goal.
Especially in web systems and smartphone apps for businesses, it is not enough for the screen to move. We need to think about authority management, data design, integration with existing systems, and ease of modification after operation.
Not to people who use AI, but to people who run AI
The future of programmers is not just about being able to use AI.
It is more important than ever to give appropriate instructions to the AI and take on the following roles:
- Review code
- Ensure quality
- Select the best technology
- Manage your entire system
AIs are good subordinates, but humans make the final decision.
For example, even if an AI-supplied implementation is working now, an experienced engineer will need to determine if future features will be more likely to fail, if there are security holes, or if operations will be able to handle them.
The value of a programmer may rather increase
AI has definitely increased the speed of development.
As a result, a single programmer will be able to handle a larger project than ever before.
In addition, if the implementation cost drops due to AI, more companies will develop "systems that have not been built with sufficient budgets until now".
In other words, even if you spend less time writing code, you are likely to create more and more.
It is difficult to eliminate the need to create mechanisms to meet on-site challenges, such as improving operational efficiency, internal tools, reservations, membership, inventory management, and adding AI to existing systems.
It's not about whether or not you use AI that matters to your customers
For those who request system development, it's not just whether or not you are using AI that really matters.
What matters is whether the completed system works safely, is easy to use, is easy to maintain, and is a good fit for the business.
Even if you are using AI, if the design is messy, it will not be a good system. Conversely, even if you are using AI, if the engineers have thoroughly checked, designed, and verified, you can develop efficiently while maintaining quality.
At Makoto Tejima, we use AI as a useful tool without underestimating design power or quality control.
We think separately about speeding up code generation and taking responsibility for finishing the system.
Summary
AI is becoming a powerful partner, not a replacement for programmers.
Here are some of the forces that will add value:
- Design Power
- Problem-solving
- Direction to AI
- Code Review Capability
- View of the entire system
The job of a programmer is not going away, but is changing from being a "writer of code" to a "leader of AI and builder of systems."
The era of AI may not be the end of the job of a programmer, but an era in which that role will greatly evolve.
At Makoto Tejima, we propose AI-powered web system development, smartphone app development, and adding features to existing systems. Please do not hesitate to contact us if you have any questions about how to proceed with the development or a quote.
