Every developer got access to the same tools at the same time. Same models, same capabilities, same power.
And what happened is the pattern you'd expect.
The developers who were already building things are building more, shipping faster, and thinking bigger. The developers who were already watching tutorials are now watching AI tutorials. The tools got better. The people stayed the same.
This pattern shows up every time a powerful new tool arrives. When YouTube launched, the people who were already teaching started making videos and reached millions. The people who were already watching TV started watching YouTube. The platform didn't create new teachers. It gave existing teachers a bigger room. The ones who had something to say and were already saying it suddenly had an audience of millions instead of dozens.
When the internet went mainstream, the same thing happened. The builders launched businesses, created content, and reached audiences they never could have reached before. The observers browsed, bookmarked, and told themselves they'd start something eventually. Same access and infrastructure, but completely different outcomes. The tool changes. The pattern doesn't.
A powerful tool doesn't change who you are. It gives you more room to be who you already were.
This isn't a judgment. It's an observation, and it matters because it tells you something important about where the value is. The value isn't in having access to the tool. Everyone has access. The value is in what you choose to do with it, how deeply you engage, and what you bring to the table that the tool can't provide on its own.
The AI will give the same quality of output to anyone who asks the same way. If two people send the same prompt with the same context, they'll get roughly the same result. So the tool itself can't be the differentiator. What separates people is everything surrounding that interaction: the understanding to ask the right question, the taste to evaluate the answer, the judgment to know what to do with it, and the willingness to actually build something instead of just learning about building something.
The person who understands the problem deeply, who knows what "good" looks like in their domain, who can evaluate trade-offs and make decisions: that person gets dramatically more out of the same tool than someone who's just copying and pasting prompts they found online. The tool amplifies the gap between them. It doesn't close it.
Some of you reading this are resistant to what I'm saying. I know because I've had this conversation hundreds of times, and the resistance always sounds the same.
"I don't need AI to write code."
Nobody said you did. But the developers sitting next to you are shipping in half the time, and they're not smarter than you. They just stopped treating a useful tool as a threat.
"It writes bad code."
Sometimes. So do you. The question isn't whether the code is perfect. The question is whether the feedback loop of generating, reviewing, and iterating is faster than writing everything from scratch. For most tasks, it is. Significantly.
"Real developers write their own code."
Real developers ship software that works. The tool you used to write it has never been the point. Nobody asks whether you used autocomplete or typed every character. Nobody will ask whether AI helped you build it either. They'll ask whether it works.
The resistance feels principled. It feels like standards. But most of the time, it's just comfort. Doing things the way you've always done them is comfortable. Learning a new way of working is uncomfortable. And it's easier to frame that discomfort as a stance than to admit that the world moved and you haven't moved with it.
I'm not asking you to abandon your standards. I'm asking you to consider the possibility that your standards and AI aren't in conflict. That using these tools well requires exactly the kind of deep understanding and craftsmanship you already value. That the developers who are best at using AI are the ones who understand software the most deeply, not the least.