
When you’ve lived in the industry long enough, you start seeing the technology world as a series of cycles. From the days I printed the first “input” to the screen with QBasic, to today where we chase data consistency in distributed systems, there is only one debate that never changes: “What is real programming?”
Back in the day, you weren’t called a developer if you didn’t know Assembly. Then C came along, and they said, “if you don’t command the operating system, you aren’t a developer.” When IDEs developed and code completion (IntelliSense) entered our lives, there were those who called it “laziness.”
Today, Artificial Intelligence (AI) and VibeCoding (coding with feeling/in the flow) concepts are in the crosshairs. I see many of my “oldschool” colleagues displaying a defensive attitude towards these tools. Cries of “It should be banned,” “This isn’t real coding” are rising.
However, this defensive attitude will not be enough to stop the approaching tsunami.
There is a very fine but vital line here. No matter how successful VibeCoding technology is right now, it is not a “magic wand.”
Especially in complex, multi-layered, and intertwined architectures; AI cannot yet flawlessly handle the “hacky” methods Senior developers resort to in order to save the moment or optimize the system all by itself.
It is a great delusion for people who know no coding or have weak engineering backgrounds to set out saying “I can do everything with AI.” Yes, they might turn out a simple interface, but when data consistency, scalability, and security get involved; it is very likely they will mess it up and produce systems that “work but are ready to explode under the hood.”
Author’s note: I am interpreting this as of today; until I publish this article, very well-trained agents and models might come out and render this paragraph completely invalid.
VibeCoding does not make a master out of someone who doesn’t understand the work. On the contrary, these tools are a massive force multiplier for developers who “understand the work” and have a solid infrastructure. If you know the architecture, AI becomes your best assistant. If you don’t, it ensures you hit the wall faster.
I love visiting ancient cities. When I look at those massive temples and columns, I always think this: We can very clearly say that the greatest wealth people possessed in that era was “time”.
The total number of soldiers participating in the Battle of Kadesh, one of the biggest battles in history, was around 50,000. Today, the number of people filling the stadium for an ordinary derby match in Istanbul is more than that. When the population was so small, competition wasn’t as savage as it is today. People could reveal those masterpieces with muscle power, years of patience, and processing stone by stone.
But today? Today the population is in the billions, and competition is ruthless. Every minute you delay and don’t pour your idea into production, someone else in another part of the world might be bringing the same idea to life.
That “abundant time” of the ancient age is gone. The scarcest resource we have today is time.
Is it cheating for someone with bad eyesight to wear glasses? Or is it a tool that reveals that person’s potential?
Let me give a more mechanical example: Hydraulic steering. Driving a truck used to require muscle power. Hydraulic steering
when it arrived, truck driving didn’t die; only the necessity for “muscle power” decreased. But softening the steering wheel doesn’t mean someone without a license can drive that truck on a mountain road.
Today, AI and VibeCoding are our hydraulic steering. It tires the master driver less, while it might cause the novice to go off the road.
I didn’t write this article to romanticize that “Artificial Intelligence is your best friend, trust it.”
The truth is; AI might not be your friend. It might even be a cold competitor that takes you out of your comfort zone and is a candidate to take your job.
But I know this clearly: AI is not your enemy. It is just a power standing there.
Handing over all your processes to AI and automating them is a choice; just as using it as a station, an accelerator tool within the “development circle” as I structured in the organization I manage, is also a choice.
My advice; don’t waste time being hostile. How you use it, where you turn the steering wheel is entirely your business. But remember, that vehicle is sitting in the garage and your competitors have already turned the ignition.
Visuals generated with Nano Banana Pro. This article has been translated from my blog post written in Turkish, with the help of AI tools during the translation process.