Right now, sitting here staring at my screen on a random Thursday morning in April 2026, I feel like I’m falling behind.

This is supposed to be the next post in my AI series – the one where I keep talking about vibe coding, turning coders into builders, and (more importantly) turning non-coders like me into builders and innovators. But today? Today this isn’t going to be another “here’s how I hacked something cool with AI” post. This is going to be an honest, chatty, let’s-be-real moment. I am tired of pretending I’ve got it all figured out. It’s changing faster than I can learn it – and yeah I am feeling some FOMO.

I’ve never felt comfortable in front of an IDE. Never. I open VS Code and my mind goes blank. I’m bad at syntax, the terminal throws errors that feel frustrating, and half the time I’m just copy-pasting whatever the AI spits out and praying it doesn’t explode in project, thankfully never really production. I can look at some of the code I’ve “built” lately and straight-up tell you: some of it is complete garbage. It’s messy. It’s inefficient. It breaks every best-practice rule in the book. I hate saying “Look at this thing I wrote” because I didn’t. I also hate the term “I Vibe’d it” – I’m using “Build” for now.

But you know what? It works.

And for me… sometimes that’s enough.

That’s the dirty little secret I don’t see a lot of people admitting out loud in this whole vibe-coding wave. We’re out here describing what we want in plain English, hitting enter, and watching magic happen. No hand-written algorithms. Just vibe. And yeah, it gets stuff done faster than I ever could on my own. But it also leaves me feeling like a hack. Like I’m riding a rocket ship I didn’t build and don’t fully understand. Thankfully no human lives on the line here.

And then I look at my friends.

Take the great John Capobianco. That guy is constantly vibing entire projects into existence. He’s out there building VibeOps communities, spinning up AI agents that feel alive, turning weekends into prototypes that actually ship. I watch what he and others are doing and I’m genuinely inspired… but I’m also hit with that punch-to-the-gut feeling: “Damn, the world just moved on again.” I finally get comfortable with GitHub Copilot and suddenly everyone’s talking about the next thing. I learn one new trick and three more drop that make it feel obsolete. It’s exhausting. Insert GooberClaw or whatever new “Claw” is out this week, I have yet to even try John’s NetClaw because frankly some of those things I just don’t trust – but somehow in a dumb way I trust my own vibe coded stuff – that’s pretty dumb.

I’m not alone in this. NetworkChuck dropped a video the other day called “I kind of hate AI… and it almost made me quit YouTube.” I watched the whole thing and just nodded the entire time. He straight-up says it: it’s a love-hate situation. The pace is relentless. Even on sabbatical he couldn’t escape it – AI was in his feed, in his conversations, in his head 24/7. He felt paralyzed. He hated that he hated it. I felt that in my bones. You nailed it Chuck.

Here’s the thing nobody talks about enough: this speed is creating real stress and anxiety.

Reaching out ot my AI Friends to help me research this one…. University studies back it up. A 2020 study by Rosenstein, Raghu, and Porter at UC San Diego (published at SIGCSE ’20) found that 57% of computer science students experience frequent impostor feelings – 52% of men and a whopping 71% of women. That was before the AI explosion. Fast-forward to 2025-2026 and a new Eastern Washington University survey of 1,000 workers shows that people using AI daily are the most likely to report regular impostor syndrome (30%). Another Ernst & Young study found 66% of employees are anxious about falling behind if they don’t use AI, and 65% are stressed about not knowing how to use it ethically.

There’s even a term for it now – technostress – and research in PMC shows AI-generated technostress indirectly tanks quality of life through spikes in negative emotions. We’re all feeling it: the pressure to keep up, the fear that if you blink you’re obsolete, the quiet voice whispering “you’re not a real builder.”

I feel that voice every single day.

But here’s the flip side – the reason I’m still writing this series and still showing up.

Vibe coding isn’t just about perfect code. It’s about democratizing building. It’s about taking non-devs like me and saying, “You don’t need to be fluent in three languages and have 10 years of LeetCode problems solved. You can describe the problem, iterate fast, and ship something that moves the needle.” It turns coders into faster builders and non-coders into innovators who never would have started.

I’m also taking steps to get others on the train and mentor others, my mentors have recently said to me “I won’t be here for ever, it’s time you start doing more” <– I am embracing this. Just yesterday a colleague talked to me about how he wished he could build something – I asked him if he had tried, then showed him 60 seconds of what’s possible – he was excited to start, and went on his way. Maybe I am more ahead than I think – there’s that impostor thing again.

Some of my code is garbage? Cool. It solved the problem in my lab in an afternoon instead of a week. John is out there vibing entire platforms into existence? Amazing – I’ll keep learning from him and cheering him on. NetworkChuck is honest about the hate part? Respect – it makes the love feel more real. These experts inspire me.

So yeah… I feel behind. I feel insecure. I feel the anxiety of “doing well” in a world that doesn’t slow down. But I’m also still here, still experimenting, still believing that “it works” is a valid starting point when you’re a systems guy who never planned on being a builder.

If you’re a non-dev reading this and you feel the same way – welcome to the club. If you’re a dev watching the vibe-coders and feeling a bit of whiplash – you’re not alone either. If you think the stuff we are building is bloated trash — you are 90% right – sometimes.

Drop a comment. Tell me where you’re at. Are you riding the wave or white-knuckling it? Let’s keep the conversation real.

At the end of the day, vibe coding was never about being the best coder in the room.

It was about giving more of us a seat at the builder’s table.

And I’m still showing up to that table – garbage code and all, still feeling out of place, still feeling behind.

(And if you’re new here, catch up on the AI series: Vibe Coding with GitHub Copilot and OpenClaw: The Passion-Driven AI Agent.)