Back in university, I built a small .NET application. I don't even remember all of what it did — some forms, some logic, a database behind it, nothing you'd put in a portfolio. By any technical measure it was tiny. A beginner's project.
I remember getting stuck — properly stuck, the kind where you stare at an error message that makes no sense and you have no idea what you did wrong. I remember googling, reading half-relevant forum answers from 2011, trying things that didn't work, and slowly, painfully, figuring it out. I remember the specific moment it finally ran — the thing I'd been fighting for hours just quietly worked — and I sat back in my chair and felt something I can only describe as pride. Real pride. I made this. I actually did something.
It wasn't about the code. It was about me. I had walked into something I didn't understand and come out the other side having understood it. That feeling was the whole reason I wanted to do this for a living.
I've been thinking about that feeling a lot lately, because I've realized I haven't felt it in a long time.
These days I build things that would have stunned that student. Bigger, more complex, more real than that little .NET project by every measure. I ship more in a week now than I probably shipped in a semester back then. By any metric you'd care to name, I am a dramatically more productive, more capable developer than I was.
I finish things — real things, things that work, things people use — and there's no moment. No sitting back in the chair. No quiet "I did that." I close the laptop and open it the next day and it all kind of blurs together into one long, flat, competent stretch of output. The days don't feel like anything anymore. They just feel like days.
For a while I assumed it was burnout, or getting older, or the shine wearing off the way it does with any job. But it's not that. I've been burned out before and this isn't it. This is something more specific, and it took me an embarrassingly long time to see what it actually was.
That's the whole thing. That's what took me so long to understand. I thought the good feeling came from having built the thing, so I assumed building bigger, better things would bring more of it. But the good feeling never came from the output. It came from the fight — from being stuck and getting unstuck, from not understanding something and then understanding it, from the friction of my own mind working against a hard problem until something gave.
The struggle wasn't the obstacle standing between me and the joy. The struggle was the joy. I just couldn't see it, because who thinks the hard part is the good part?
And here's what changed, quietly, without me noticing when: the struggle is mostly gone now. I describe what I want, and it appears. I hit something I don't know, and I don't sit with the not-knowing anymore — I ask, and the answer is just there, complete, before the confusion ever has time to become the thing I push against. The wall I used to climb has been demolished, helpfully, in advance.
Which sounds like a gift. It ships faster. The code is often better than what I'd have written stuck at 2am. But the wall was where the feeling lived. Take away the wall and you take away the climb, and it turns out the climb was the part I loved. I optimized away the friction, and the friction was the point.
I don't think this is just me. I think it's happening quietly to a lot of us, and we're not really talking about it, because it feels ungrateful to complain that your job got easier.
But something real is going. The small, private satisfactions that made this feel like a craft instead of an assembly line. The bug you chased for three hours and finally cornered. The elegant little solution you found yourself and were quietly proud of all day. The thing you understood so deeply it started to feel like it was part of you. Those moments are getting rarer, because the machine is very good at producing the output of those moments and completely unable to give you the moment itself — and the moment was always the reason.
In tech, we're slowly losing the things that were ours. The hard-won, personal, slightly private sources of joy that had nothing to do with productivity and everything to do with why we got into this. And because what replaces them is faster and shinier and more impressive, we're calling it progress, and mostly we're not admitting that something we loved is leaving in the trade.
This is the part where a post like this is supposed to turn around and offer you five ways to fall back in love with coding. Do a passion project. Code without AI on weekends. Rediscover your spark.
I'm not going to do that, because I don't believe it, and I think you'd know I was lying.
The truth is you can't un-know that AI exists. You can't really opt out — the pace of the work assumes it now, and "just struggle for fun on your own time" doesn't survive very long against a job that measures you on output. And even when I do deliberately do something the hard way, it's not quite the same, because I know the easy way is sitting right there and I'm choosing the friction on purpose. Manufactured struggle isn't the same as the real thing. The innocence of having to figure it out — that's gone, and you can't fake your way back into it.
So I'm not going to tell you how to get the feeling back. I don't know how. I'm not sure it comes back.