No-Code Issues: The Importance of No-Code AI as an Essential CTO Strategy
Why should every CTO prepare for 'no-code AI' going forward?
"In my time as a CTO, I've never seen anything quite like this moment. The very concept of software development is shifting beneath our feet."
Forbes Technology Council, Ryan Frankel
On one hand, we're seeing unprecedented productivity and creativity growing at a rapid pace. Thanks to remarkable tools that can turn a few ordinary words into functioning code in an instant.
But on the other hand, as people's roles, development standards, and the very concept of 'developer' are being shaken, the future is becoming increasingly uncertain.
Charles Dickens probably didn't imagine something like today's artificial intelligence when he wrote "It was the best of times, it was the worst of times." Yet this phrase fits today's situation eerily well.
The emergence of 'vibe coding,' a term coined by Andrej Karpathy, is not just a technical milestone — it's driving a new cultural shift.
Tools like Lovable and Bolt, which were once unimaginable, now enable even people with zero coding experience to easily build software themselves.
While these tools aren't perfect yet, they are undeniably changing the expectations of both professionals and general users.
Let me show you how easy it is to build something. I created a tool that checks whether text was written by a human or AI.
I simply requested "Build a tool that determines whether pasted text was written by a human or AI," and the tool was completed in 2 minutes.
Honestly, I'm not sure how accurate it is, but feel free to try it yourself. Isn't it amazing how quickly you can build something?
New Opportunities + New Challenges for Non-Technical Entrepreneurs
'Vibe coding' is attractive not simply because non-developers can build software.
It means you can now build and use services yourself that companies would never release to market because they're too specialized and customized.
For example, if I were a gig worker, I'd build a tool that aggregates notifications from multiple apps into one place and tells me which app and which job would maximize my earnings.
I could even exclude specific areas I personally dislike.
We're truly entering an era where idea-rich people without any coding experience can become entrepreneurs. Even the famous startup incubator Y Combinator has noted that this change is happening in a big way.
YC CEO Gary Tan recently said in an interview, "About a quarter of startups in YC right now are using code where 95% was written by AI tools."
Of course, development tools leveraging generative AI will keep getting better. However, there are still clear limitations and challenges.
When non-technical users encounter errors, they often can't fix them properly on their own, and the problems can 'snowball' until the entire project falls apart.
Security is another concern. These tools don't have security built in by default. They sometimes use publicly available external libraries, which can create security vulnerabilities.
You must be very careful when handling important information or sensitive data.
No-Code AI as an Essential CTO Strategy: What Will Happen to Web Developers?
Developer jobs themselves probably won't disappear, but the nature of the work will likely change. Certain tasks in particular will see sharply reduced demand, and other roles will also shift somewhat.
At least in the near future, I don't think we'll see fully automated coding powered by AI alone.
Even if such an era arrives, someone will always be needed to instruct AI on what to build and how, integrate various components, and manage infrastructure.
Just as the automotive industry evolved when automation was introduced, developers now need to learn and actively embrace new tools.
Experienced professionals may actually see 'vibe coding' as helpful rather than threatening. They can delegate tedious repetitive coding, testing, documentation, and architecture scaffolding to AI, freeing them to focus on what truly matters.
However, creating stable, error-free production software ultimately still requires 'human hands.'
As an IBM meeting memo from 1979 stated, "A computer can never be held accountable for its decisions, so the final decision-maker in important matters must always be a human."
The real concern is that the number of entry-level developer jobs could shrink dramatically.
As simple tasks typically handled by junior developers are rapidly replaced by AI, companies will increasingly seek to hire only experienced senior developers.
If this continues, the pipeline for developing skilled senior developers in the future could become insufficient.
A Future Where Everyone Can Freely Build Software
The biggest change brought by vibe coding is that anyone can now easily build software. The implications of this for the future are as diverse as your imagination.
- Increase in Cyber Attacks: Even without technical skills, people can create dangerous phishing web pages. For example, a single sentence like "Make something that looks exactly like the Facebook login page" could produce a phishing site.
- More Inclusive and Diverse Software: Customized services that closely reflect the lifestyles and needs of diverse populations could emerge.
- Legal Confusion and Patent Issues: Who should be considered the owner of intellectual property for software built with no-code?
- Increased Logical Thinking: As more people build software themselves, their logical thinking abilities improve. Even in fields unrelated to technology, the ability to systematically analyze problems and find logical solutions could be enhanced.
Ultimately, thanks to new AI tools, the future is approaching ever faster. Vibe coding has both benefits and drawbacks, but I'm personally excited that many more people will get to experience the joy of building software.
Why not prepare for this change together?
IMPAKERS Blog | What's the outlook for no-code/low-code web apps? Read more
Source: Forbes Technology Council, Ryan Frankel, Forbes, "Why Every CTO Should Be Planning For No-Code AI", https://www.forbes.com/councils/forbestechcouncil/2025/05/12/why-every-cto-should-be-planning-for-no-code-ai/, (2025.03.27)