Will AI take your job? Possibly.
Can you do something about it? Absolutely.
Wait wait, before you assume this is just another “vibe coding” motivational slop, I promise, it’s not.
I use LLMs all the time; for ideation, boilerplate, and prototyping. But I don’t vibe code. Even if I did, I’d still outperform most because of the fundamentals I’ve been sharpening since 2018.
I have two goals with this post:
- Help you move past the fear of AI, it’s legit crippling.
- Remind you that X (Twitter) is not a real place, it's mostly noise.
Why should you listen to me?
Because I’ve been there; paralyzed. This is the second time I've watched the “end of programming” panic unfold. The first was during the no-code wave when I got started.
But after building and embedding an agentic tool into my system, and learning how LLMs actually work; I saw it clearly:
It’s mostly noise.
Here's What I Built
I’ve got an LLM embedded deep in my OS. It can fetch my goals, check my calendar, trigger reminders, do stealth research all automated via timers and conditions. For demo purposes, I’m manually triggering it here:
And yeah, these tools are good. But not on their own.
Even if they were perfect, they’re missing the one thing we have:
The Feeling.
The intuition that only comes from touching grass, experiencing real things, and solving actual problems.
If anything, the great engineers aren’t losing jobs; they’re taking more of them.
This tweet says it best:
A Word on “Vibe Coding”
The first time I saw “vibe coding” was from Andrej Karpathy on X.
If you don’t know Andrej, he’s a genius.
He made a 4-hour video walking through GPT-2 (124M) from scratch; and people are literally donating in the comments just to say “thank you.” That’s how clear and compelling he is.
I watched it in one sitting. Teaching is hard. Teaching transformers without boring people? Nearly impossible. But he did it.
Now here's the wild part:
The term “vibe coding” has been hijacked.
We’ve got people building landing pages, calling themselves Tony Stark because they prompted an LLM and slapped Tailwind on it. It's funny; but also sad.
Tony Stark wasn’t Stark because of JARVIS. It was his brain. His curiosity. His engineering skill.
If JARVIS made Tony, then Ant-Man; who's lovable but not the sharpest tool; could be Stark too. All he’d need is JARVIS, right?
But without someone like Tony to guide it, JARVIS is just a fancy shiny tool.
The tool is only as good as the operator.
Andrej is Tony because he thinks at that level. And the LLM simply reflects that.
You’re afraid of LLMs because deep down, you know you’re not as good at your craft as you could be.
That’s not to be mean; that’s an invitation.
1. Fear
You’re scared because you either don’t understand these tools, or; respectfully, your work is mostly boilerplate.
Antidote? Get really good at something.
If you’re a web dev, start building tools for web devs.
Backend API dev? Learn to build runtimes, infra, orchestration tools.
Write software that doesn’t decay.
Jonathan Blow on Software Decay:
Casey Muratori on Software Decay:
This is what I did in my first job:
I took a 4GB dependency bloatware, trimmed it down, built internal tooling around it, and now it's stable and lean. No unpredictable dependency updates. Just clean systems.
I’ve always been curious about what’s “behind.” I can stub out a working message broker in plain JavaScript without breaking a sweat. That’s not magic; it’s deep work.
For instance:
Right now I’m building a realtime UI in C++ (don’t ask). Sure, I brainstormed with an LLM, but I caught the scaling issues early. I guided the LLM, not the other way around.
Eventually, I landed on a sparse set structure to manage real-time rendering safely.
Now be honest: how many “vibe coders” right now on X you think can guide an LLM toward thread synchronization with lockable queues and segmentation fault isolation?, while making sure texture for images are created before the next render tick?
in separate threads?
Yeah.
So, get good. Really good.
And you’ll realize: Twitter is mostly noise.
2. Go Beyond the Noise
The loud ones!
You’ve seen this in teams. There’s always that dev, loud, confident, seems smart. But listen closely and it’s all fluff.
The real dev? Quiet. Precise. Rewrites their code at night so no one’s feelings get hurt.
The same thing is happening on X. The loudest voices are usually the wrongest. And they’re selling slop.
“Twitter isn’t a real place” is a meme; but it’s also true.
So shut out the noise. Focus. Build real stuff.
But if I had to give a call to action:
Be loud, and right.
3. Build in Public (But for Real)
There was a time I was horrible at communicating. I'd avoid interviews like the plague, so I just build a demo and hope it spoke for me.
But over time, I’ve been learning to talk more, write more (like this post you’re reading).
Back in the day, “build in public” meant something. It was engineers sharing breakthroughs, struggles, tools.
Today? MMR slop. AI slop. Useless polls. Vibe-farming tweets.
New devs are being fed garbage. No real inspiration. Just noise.
Let’s take it back.
Let real builders reclaim the space.
Share your work. Write about what you’re building. Tweet about your experiments. You never know who’s watching.
Honestly, this advice is for me too. I’ve been sitting on drafts, working up the nerve to hit “post” on x
Let’s do it anyway.
socials:
X
More Content:
Top comments (2)
This Will literally Change your Perspective on LLM's
From a black-box to an actual understanding!
Maybe yeah but I don't know
Some comments may only be visible to logged-in visitors. Sign in to view all comments.