Vibe coding has been around longer than we think...
I once asked a developer to explain his code when it broke due to edge cases. He told me he didn't know because he copied it from Google. At least he was hon...
I once asked a developer to explain his code when it broke due to edge cases. He told me he didn’t know because he copied it from Google. At least he was honest.
For years, some developers got by with Google and Stack Overflow. They copied snippets, patched things together, and shipped code without really understanding it.
It is not easy to identify them as “vibe coder” back then. They disguised as software engineers, as clients and business people can’t tell the difference.
Now with LLMs, the barrier of entry to vibe coding has dropped even further. Anyone can throw prompts at AI and get somewhat working code.
That’s why many of them who built careers on blind copy-paste are now losing their jobs. AI does that kind of vibe coding faster and cheaper.
The ones who’ll thrive are the engineers who can do more than vibe code—they can architect, reason about trade-offs, and review code with a deep understanding.
👉 In an AI era, vibe coders who disguise as software engineers get replaced. True software engineers stay valuable.
What’s your take? Have you seen this shift happening in your team or company? How are you ensuring you’re building real engineering skills rather than just getting good at prompt engineering?
#GenAI #VibeCoding #LLM #Cursor #ClaudeCode
Enjoyed this? Subscribe for more.
Practical insights on AI, growth, and independent learning. No spam.
More in Vibe Coding
Congrats to Cohort 4 of my Foundations of Claude Code workshop, who wrapped on 18 June.
Wai Soon, wai siong, Hanah, Daniel Ling, chee shen, Mary Gagahina, Veronica Loh, Natalie, Terence Kok, Kah Meng, Yasmeen, Swee Chye
Claude Code Foundations: 5 Lessons from Cohort 1
To the learners who signed up as "guinea pigs", thank you. The first cohorts are always the messiest, as the course content and timing have not yet been test...
Am I the only one feeling uneasy building AI agents with OpenCrawl after testing it for a while?
I've been building AI agents before OpenClaw, and building skills using Claude Code for a while. It's powerful. When I learned about OpenClaw, I knew exactly...
UX/UI and naming matter more than capability for adoption.
Recently, everyone on LinkedIn is talking about learning Claude after the demo of Claude Cowork.
3 months ago I posted "Vibe coders, this will happen to you sooner or later."
The post went viral:
We were promised autonomous AI agents. But got Workflow Automation 2.0 instead.
2025: The Year of AI Agents 😄
Congrats to Cohort 4 of my Foundations of Claude Code workshop, who wrapped on 18 June.
Wai Soon, wai siong, Hanah, Daniel Ling, chee shen, Mary Gagahina, Veronica Loh, Natalie, Terence Kok, Kah Meng, Yasmeen, Swee Chye
UX/UI and naming matter more than capability for adoption.
Recently, everyone on LinkedIn is talking about learning Claude after the demo of Claude Cowork.
We were promised autonomous AI agents. But got Workflow Automation 2.0 instead.
2025: The Year of AI Agents 😄
Claude Code Foundations: 5 Lessons from Cohort 1
To the learners who signed up as "guinea pigs", thank you. The first cohorts are always the messiest, as the course content and timing have not yet been test...
Am I the only one feeling uneasy building AI agents with OpenCrawl after testing it for a while?
I've been building AI agents before OpenClaw, and building skills using Claude Code for a while. It's powerful. When I learned about OpenClaw, I knew exactly...
3 months ago I posted "Vibe coders, this will happen to you sooner or later."
The post went viral: