I think I've stopped writing code.
Not in the dramatic, throw-your-keyboard-away sense. More like the slow realization that the thing I've done every day for 25 years has quietly shifted underneath me, and I didn't notice until it was already different.
I've been building software since I was 15. No college, no bootcamp -- just a kid who figured out that if you typed the right things into a text editor, you could make a computer do stuff. That discovery shaped everything. My career, my identity, how I think about problems. "I write code" wasn't just what I did. It was who I was.
Then AI got good at writing code too.
The part nobody talks about
There's a conversation happening in private that isn't happening in public. Experienced developers -- people with 10, 15, 25 years in -- are watching AI generate in a minute what used to take them an hour. And a small voice keeps saying: what was the point of all those years?
Nobody posts about it. Because admitting it feels like weakness. You're supposed to be the senior dev. The one who's seen it all. You're not supposed to be the one quietly wondering if your career just became a hobby.
I know because I'm one of them.
What I actually learned
Here's the thing, though. The more I use AI to write code, the more I realize that knowing how to code is the thing that makes AI useful. The 25 years aren't wasted -- they're the context window.
You can't debug what you don't understand. You can't architect what you haven't built. You can't spot the subtle wrongness in generated code unless you've written enough wrong code yourself to recognize it.
The experience isn't obsolete. It's the operating system that makes the new tools actually work.
But that doesn't make the identity crisis less real. It just makes it more interesting.
The merge conflict
In git, a merge conflict happens when two branches change the same thing and the system can't automatically reconcile them. You have to look at both versions and decide what to keep.
That's what's happening to experienced developers right now. Two versions of your professional identity are trying to occupy the same space: the one you built over decades of writing code, and the one that's emerging as AI changes what "writing code" even means.
Nobody can auto-resolve this for you. You have to look at both versions and decide what to keep.
Working through it out loud
I started The Merge Conflict because I needed a place to work through this out loud. Not a course, not a tutorial, not another "AI will change everything" hot take. Just an honest space for experienced developers who are navigating the same thing.
If that sounds like you, come sit by the fire.