On my way home from the airport recently, my Uber driver started asking me about AI. He wasn’t asking for himself — he has kids heading to college and he’s genuinely worried about what the world looks like for them by the time they graduate.
I get it. Students come to me with the same anxiety all the time: “Is AI going to take my job? Is a development career even worth starting anymore?”
Honestly? The experts don’t have a clean answer either. A recent LinkedIn News story put it well — “Will AI take your job? It’s complicated.” And if experts with all the data are saying it’s complicated, maybe we should stop expecting a simple yes or no.
But I’ve been in the trenches. I’ve been vibe coding real applications with AI. I’ve seen it work brilliantly and I’ve seen it fail completely. So here’s my take — not from a report, but from actually building things.
First, Let’s Take a Step Back
Before we get into AI, I want to zoom out. Because we’ve been here before.
The Paper Era — Information lived on paper. People wrote by hand, organized filing cabinets, analyzed things manually. That was the job.
The Computer Era — Computers arrived and critics feared mass unemployment. Instead? Entirely new industries appeared. More jobs, not fewer.
The Internet Era — Computers + Internet turned the world into a global village. Information was democratized. Anyone with a connection could access what once lived only in expensive libraries. E-commerce, remote work, the gig economy — none of it existed before this wave. And again, the economy grew.
Here’s the pattern every time: technology automated the repetitive, and humans moved up. The tools changed. The need for human intelligence didn’t.
I believe that’s exactly what’s going to happen with AI.
What I Actually Learned from Vibe Coding
I recently built a couple of applications using AI — just describing what I wanted and letting AI write most of the code. Here’s my honest experience:
When it worked brilliantly
I had a list of prototype apps I’d been meaning to build for months. The usual developer problem — you know what you need to build, but there’s so much boilerplate involved that you never actually start. (Every developer reading this has bought a domain for a project they never shipped. You know who you are. 😄)
With AI, I shipped those prototypes in 1–4 hours each. Without AI, double the time — and honestly, I probably would have never started.
AI didn’t just speed me up. It unlocked projects I’d been sitting on forever.
When it struggled
I tried to vibe code a module inside a CMS using an SDK I wasn’t familiar with — not my primary stack, not a standalone app. It went sideways. The AI kept generating plausible-looking code that didn’t actually work in that specific context.
The lesson? AI amplifies your existing knowledge. It’s a force multiplier, not a replacement. When I paused, spent time understanding the basics of that SDK myself, and then brought AI back in — it worked out really well and saved significant time.
You still need to know how to fly. AI is a great co-pilot, not the captain.
The “AI Theater” Problem — And Why It Matters for You
Here’s something worth knowing: a McKinsey survey of 1,400 executives found that 90% of companies claim they’re “using AI” — but only 23% have actually scaled it to create real business value. Blake Crosley wrote a brilliant piece calling this “AI Theater” — organizations that invest visibly in AI through announcements, pilots, and hiring without actually creating measurable outcomes.
Why does this matter for your career? Because the companies that are genuinely using AI well are pulling ahead — and they need people who can tell the difference between AI theater and AI that actually works. That judgment is human. That skill is yours to develop.
Knowing how to actually use AI to ship real things, not just demo impressive prototypes, is going to be one of the most valuable skills of this decade.
So Will AI Take Your Job?
Here’s my honest answer: it depends on what your job actually is.
A recent CNN Business report put it well — AI is automating parts of jobs, not entire jobs. McKinsey estimates AI is technically capable of automating 57% of work-related activities. But “technically capable” and “actually replacing your role” are very different things.
Companies are using AI to automate certain parts of jobs rather than replace entire positions — business leaders are figuring out what AI can and can’t do, and recalibrating jobs around responsibilities that only humans can do.
If your job is purely repetitive — following a script, copying data, generating the same output with no real judgment — yes, AI can and probably will do that.
But if you learn how to use AI, keep growing your expertise, and keep your brain in the game? Your job isn’t going away. It’s evolving.
And here’s the good news LinkedIn’s data actually backs this up: AI has already created over 1.3 million new roles — AI Engineers, Forward-Deployed Engineers, Data Annotators — and AI Engineer is one of the fastest-growing job titles on LinkedIn over the past three years.
The wave creates jobs. It always has.
What Your Clients Will Expect — And Why You’re Still Needed
Future client expectations are going to shift — and this is important. Every client will still need developers, consultants, agencies, and builders to create their apps, software, and websites. That part isn’t changing.
What is changing is their benchmark. They’ve seen what AI can do. They’ll expect faster delivery and more cost-effective solutions. The developer who can use AI to deliver better quality faster is the one who wins that client.
Think of it this way: a few years ago, knowing a framework like React was a differentiator. Soon, knowing how to build effectively with AI will be the differentiator. Get there first.
The Real Question: What Are You Doing Today?
Nobody — and I genuinely mean nobody — knows what the world looks like in 10 years. Not the analysts, not the CEOs, not the people building these models. Stop worrying about a future no one can predict with certainty.
Economists, professors, and advisers discussing AI’s impact on jobs all say things are uncertain — there is no clear answer. If that’s the expert consensus, maybe the energy is better spent on what you can control.
What you can do right now:
Audit your daily tasks. Which ones are repetitive and mechanical? That’s where AI can take load off your plate — so you can focus on the work that actually needs your brain.
Start experimenting. You don’t learn AI by reading about it. Build something. Even something small. Fail at it like I did with that SDK. Learn, then try again.
Keep your fundamentals sharp. AI amplifies knowledge. The more you genuinely understand your craft, the more powerful your prompts, your judgment, and your output become. The people struggling with AI-assisted coding are often the ones who skipped the fundamentals.
The need of the hour is simple: adopt and adapt.
One Thing I’m Keeping an Eye On
All of this assumes AI stays accessible — and right now, AI tokens are a new kind of fuel. Running large models is expensive, and that cost gets passed on.
I’m confident this will change. New chips, more efficient models, better infrastructure — the economics of AI will shift, just like they did for cloud computing, for storage, for bandwidth. There’s even a real possibility we’ll be running capable models locally on our own laptops someday. That would be a game changer for access and cost.
But even today, the direction is clear and the momentum is real.
The Optimistic Take
To the Uber driver’s kids. To the students asking me if development is a dead-end career. To anyone anxious about where this is all going:
The computer didn’t end careers. The Internet didn’t end careers. AI won’t end yours either — if you’re willing to learn alongside it.
The World Economic Forum projects that while AI and automation may displace some jobs, it’s also expected to create millions of new positions — pointing to a shift in the division of labor rather than outright elimination.
Every technological wave rewards the people who ride it early. The ones who lean in, stay curious, and keep building.
The future belongs to the humans who know how to work with AI. Not the ones waiting to see if it goes away.
It’s not going away. And honestly? That’s great news.
What’s your experience with AI in your own work? I’d love to hear — drop a comment below!
References: