The Journey That Was
A few years ago, building the frontend for my app was a journey. I'd sit down, get into the zone, and wrestle with the code. There was frustration, sure, but there was also a deep, electric excitement when it finally came to life. I wasn't just building a feature; I was learning, problem-solving, and growing.
Today, I can't do that anymore.
The New Reflex
I can't sit down and write code for a side project or even a crucial piece of work without immediately reaching for AI. My first thought isn't "How do I solve this?" It's "What prompt do I write?"
It feels like a superpower has been grafted onto my workflow. But lately, I've started asking a terrifying question: Is this power making me weaker?
Here's My Confession
1. I've lost the ability to just... start.
The blank editor window now induces anxiety, not possibility. My reflex is to populate it instantly with an AI generated scaffold. The act of creation has been outsourced.
2. My "debugging patience" has evaporated.
Staring at an error for 15 minutes? Unthinkable. I paste it, get the fix, and move on. I get the "what," but I'm losing the "why." That deep, structural understanding that comes from the struggle is gone.
3. My most improved skill isn't coding—it's prompting.
I'm a more efficient manager of an AI, but I fear I'm becoming a less competent engineer.
4. And here's the weirdest side effect: I feel stagnant.
This was my original worry. I'm moving faster than ever, but I feel like I'm running in place. I'm not pushing my own boundaries; I'm just instructing something else to do it. The fatigue I feel isn't the deep burnout from intense focus—it's the shallow exhaustion of constant context-switching and prompt-tweaking.
The Paradox
It's a paradox: the tool designed to eliminate friction and blockers might be creating the biggest blocker of all—a stunted, impatient, and dependent developer brain.
I'm not saying AI is bad. It's revolutionary. But like any powerful tool, it demands intentional use. Right now, I'm on autopilot, and it's leading me straight into a skill ceiling.
I Suspect I'm Not Alone
So I'm putting this out there to our community:
- Have you felt your own attention span for deep coding work shrink?
- Do you miss the "deep flow" state, or has AI replaced it with something more frantic?
- Most importantly: How are you fighting the brainrot? How do you balance the insane leverage of AI with the need to keep your own skills sharp and your curiosity alive?
My Small Rebellion
I'm starting small. I'm trying "no-AI" coding hours. I'm forcing myself to read the official docs again. I'm building a tiny, stupid project with no goal other than to remember what it feels like to think for myself.
This isn't a rant against AI. It's a plea for awareness. Let's talk about the cost of the shortcut before we forget what the long road even feels like.
Damn. I'm cooked. I couldn't even have written this post without ChatGPT 💀
.
Top comments (0)