You're Protecting Your Comfort Zone
Stop Hiding Behind Code You Memorized and Start Building Something Real
It’s 11pm. Xcode is open. You’re staring at Swift syntax you’ve never written in your life, and some voice in the back of your head is telling you to close the laptop and come back when you “know more.”
Instead, you type a prompt.
That’s vibe coding. And yeah, traditional developers lose their minds over it.
“That’s Not Real Programming”
I get it. I’ve been writing software for 25 years. I understand the instinct to protect the craft. But let’s be honest about what’s really happening when experienced developers dismiss AI-assisted development as “not real programming”, they’re not protecting quality. They’re protecting identity.
Stoics would recognize this immediately. Marcus Aurelius didn’t waste energy fighting things outside his control. He focused on what he could actually influence. AI’s advancement? Not in your control. Market disruption? Not in your control. Your willingness to learn, adapt, and leverage new tools? That’s yours. All of it.
The dichotomy of control isn’t just a philosophical concept, it’s a survival skill for developers right now. Clinging to the idea that your value lives in syntax you memorized is like a blacksmith in 1910 insisting that anyone who uses a power tool isn’t a “real” craftsman. Meanwhile, the guy with the power tool is building three times as much.
Vibe coding (describing what you want and iterating with AI until it exists) isn’t the end of real software development. It’s a new tool that reveals something uncomfortable: who’s been coding for the joy of creation, and who’s been hiding behind gatekeeping complexity.
My Experiment: Building an iOS App in a Language I Barely Know
Here’s where I put my money where my mouth is.
I’ve done iOS development before, mostly in Objective-C. Swift? Not my world. But I had a clear idea for a savings rate dashboard app, something genuinely useful, something I wanted to exist. So instead of waiting until I’d done six months of Swift tutorials, I started building it. With AI as my co-pilot, breaking down the work into pieces I could actually manage.
This isn’t theory. This is me, right now, figuring it out as I go.
And here’s what I’ve learned: the AI doesn’t care that I’m rusty on Swift. It handles the boilerplate. It handles syntax I’d otherwise have to look up a dozen times. What it can’t do is decide what to build, why it matters, or whether the architecture makes sense for the long haul. That part is still on me. That part will always be on me.
Not knowing Swift became irrelevant when I could prototype, test assumptions, and ship an MVP in days instead of months. Note: I’m about a week away from submitting version 1 to the app store.
Aimless Prompt Thrashing Is Not a Strategy
Let me be clear about something, because I see this mistake everywhere: you cannot just wing it.
The idea that you can magically build something by dumping vague prompts into an AI is naive, and it leads to a chaotic mess of half-working code you don’t understand.
What actually works is treating AI the way you’d treat a capable junior developer. You wouldn’t hand a junior a vague task and disappear. You’d give them a clear objective, a defined scope, and enough context to succeed. Then you’d review their work and course-correct.
Before I type a single prompt on this iOS project, I have a build plan. Clear goals. A tech spec. Tasks broken into pieces small enough that the AI can actually shine on them. That preparation is what separates productive AI-assisted development from burning three hours to produce garbage.
The AI handles the heavy lifting. I handle the vision and the judgment. That’s the deal.
The Anxiety Tells You Everything
If reading about AI replacing developers makes your stomach drop, that anxiety isn’t about AI. It’s a signal that you’ve tied your professional identity to syntax memorization instead of problem-solving ability. And that’s worth sitting with for a minute.
Think about what you’re actually afraid of losing. Is it your ability to solve hard problems? To understand systems, architecture, business logic, user needs? Because AI isn’t touching any of that. Or is it the ability to write a for-loop faster than a junior dev, or recall the exact method signature without checking docs?
Because one of those things matters. The other one never really did.
Software engineering has always been about solving problems, understanding what the business needs and delivering something that works. The language was always just the vehicle. Developers who lose sight of that are the ones who’ll struggle, not because of AI, but because they were already optimizing for the wrong thing.
Epictetus had a line that applies here: it’s not things that disturb us, but our judgments about things. AI isn’t the threat. The judgment that your value is tied to irreplaceable technical obscurity—that’s the threat.
The Developers Who Will Thrive
They’re not the ones who know the most languages.
They’re the ones who solve valuable problems regardless of the tools available. They adapt. They stay curious. When a new tool shows up, they ask “how can I use this?” instead of “why is this bad?”
As a solo developer, I’m juggling marketing, product development, customer support, and feature building all at once. Leveraging AI to handle some of that load while I stay focused on long-term strategy isn’t laziness, it’s leverage. It’s the same reason senior engineers use frameworks instead of writing everything from scratch. You use the tools that let you build more, faster, without compromising on what actually requires your judgment.
This savings rate app isn’t just a side project. It’s proof that your ideas can become real without waiting for perfect knowledge. It’s proof that “I don’t know Swift well enough” is a story you’re telling yourself, not a fact about the world.
So Where Does That Leave You?
Fighting AI’s role in development is like resenting gravity. It’s here. It’s changing things. The only real question is whether you’ll adapt with curiosity or resist with fear.
You can’t control what AI does to the industry. You can control whether you pick up the tool and figure out how to use it well.
I’m still figuring it out. The Swift app isn’t done (although it is really close). Some days the AI output needs serious rework. Some days it nails exactly what I needed in thirty seconds. That’s the process. And honestly? I’m having more fun building than I have in a while, because I’m back to focusing on the part that actually matters: the problem, not the syntax.
So here’s what I want to know from you:
What’s the AI fear you’re still holding onto and what would it take to let it go?
Drop it in the comments. You might be saying exactly what someone else needs to hear.
Quote of the Day:
“The impediment to action advances action. What stands in the way becomes the way.” - Marcus Aurelius
👉 If you enjoy reading this post, feel free to share it with friends!
Or feel free to click the ❤️ button on this post so more people can discover it on Substack 🙏
You can find me on X and Instagram.
Also, I just launched a new YouTube channel - Code & Composure