I’ve been thinking about this for a while.
And honestly, it hit me that coding just doesn’t feel the same anymore. Not completely. There’s something different in the way we write code today and the way we approach building things, and it has a lot to do with AI.
When I first started coding, everything felt alive. Your first real project, the first time you built something that actually did something cool, that was all yours.
You started with a blank page in your IDE, typed out every line, and figured out each problem. CSS wouldn’t cooperate, the logic would fail, and the bugs would drive you nuts, but when it finally worked, you felt it.
That “I did this” feeling.
Now, AI changes that.
Don’t get me wrong, it can be incredible. I’ve used it to speed things up, to scaffold projects that would have taken days. And when I’m burnt out, it’s a lifesaver.
It lets you create faster, and it lets you try things you couldn’t before. There’s a spark there, I won’t lie. But it’s different. It doesn’t feel like yours.
And that’s the thing. The more I use it, the more I notice that a lot of what I build doesn’t give me that same satisfaction. Even if I understand everything, even if I guide it, the final product is not fully mine.
And I realized that’s not just me being picky. That’s how a lot of developers feel now.
It’s quantity over quality
Some might say, “Well, just don’t use it. No one’s forcing you.” But the truth is the industry kind of is. Companies, agencies, and even small teams—everyone expects developers to use AI to be faster and to keep up.
If you don’t, you fall behind. It’s quantity over quality, speed over the long, messy, creative process that used to define coding.
And I feel it. We’re all adapting, whether we like it or not. It’s not about rejecting AI; it’s about figuring out how to still feel ownership and how to keep some of the joy in building. Because that feeling is what keeps us going.
I don’t let AI replace my thoughts
So now, I try to think about it differently. I don’t let AI replace my thoughts in the things that matter. I use it for staging, for boring repetitive stuff. But the logic, the architecture, and the vision stay mine. I want to still feel like I built something, even if AI helped with the scaffolding.
For people just entering the field, I get it. It must feel confusing. How much should you rely on AI? How much is too much?
Honestly, no one has the perfect answer yet. But my advice is this: learn the craft first. Understand the code.
Use AI as a tool, not as a shortcut around thinking.
I also want to say, it’s okay to feel nostalgic about the old days. I do. Sometimes I miss the slow nights figuring out code from scratch, the messy victories, and the feeling that you owned the project fully.
But we can’t go back. We adapt. We find new ways to feel that ownership, even in a world where AI speeds everything up.
Parts of coding that matter
And maybe that’s the lesson for all of us. It’s not about resisting the change. It’s about keeping the parts of coding that matter, the parts that feel like yours. Because that feeling is what keeps us coming back, what keeps the work meaningful.