The non-engineers are using AI to build the things you used to get hired for. I'm an engineer telling you to go take their side of the fence; mostly because I'm failing to do it myself.
There is a particular face an engineer makes when they open somebody's shipped product and see the code underneath. You know the one, you open the console, check the headers from their responses, how they handle authentication, passwords probably plain on the table. There is an API key sitting in the frontend. And the person who built it? Not an engineer. A marketer. A sales person. Somebody who, two years ago, would have had to hire you to get any of this done.
And here is the part that stings: it works. People are paying for it. Real money, every month.
I want to talk to my own people for a minute. The engineers. And I want to be honest that I am talking to myself first.
We have spent a long time behind a fence. The fence was real; it was made of syntax, of setup, of all the boring knowledge that took years to earn. You couldn't ship a product unless you could build it, and you couldn't build it unless you were one of us. That fence gave us salaries, leverage, a certain quiet pride. It also made some of us lazy in a way we don't like to admit. We confused knowing how to build with having built something people want.
The fence is down. AI took it down. And the marketers walked straight through.
So now we sit and we critique. We screenshot their design and arch decisions and share on X. We say "but it won't scale," "but security," "but wait till they get real traffic.". "you don't need that database & x service" And sometimes we are right. The engineering is not solid. It will crack somewhere. But be honest with yourself about what that critique actually is. It is the sound of a man watching someone eat while he explains why the food is not properly seasoned.
Here is what I actually think, and why I'm writing this.
They did not beat us at engineering. They beat us at shipping. Those are not the same skill, and we pretended they were because it flattered us. The marketer knew a thing we often don't: who the customer is, what they'll pay for, how to put the thing in front of them, how to close. That was always their yard. AI just gave them a bridge into ours.
And the bridge goes both ways. That's the whole point. The same AI that let a sales person build a working app can let me - who actually understands systems, edge cases, what happens at 3am when it breaks - do the part I always outsourced or avoided. The landing page. The cold outreach. The pricing. The launch. The customer conversation I find awkward and somehow beneath me.
Let me tell you where I actually am, so this doesn't sound like advice from a mountain.
I am struggling with this. I can build the thing in my sleep. I have built plenty. But every time I get to the edge of my yard; the part where I have to put a price on it, write the post, message the ten people who might pay; I freeze. I go back and refactor something nobody asked me to refactor. I tell myself I'll launch when the code is cleaner. The code is already clean. That is not the problem. The problem is that the selling side is their skill, the one I never built, and I am scared of being bad at it in public the same way they should have been scared of shipping ugly code; except they weren't. They just shipped.
That is the thing I keep coming back to. They were not more talented. They were more willing to be bad at something in front of people. And it worked.
So I'm not writing this from the finish line. I'm writing it from the middle of the bridge, trying to make myself keep walking. Pick one small thing. Something you've been able to build for years and always assumed "somebody else" would take to market. Build it small small. Then do the uncomfortable part yourself; the price, the post, the ten messages; and use AI for the parts that scare you, exactly the way they used it for the parts that scared them.
Because here is where this ends up if we don't move. They keep crossing the bridge, getting better at the engineering, hiring one real dev to firm up the cracks. And we stay behind a fence that no longer exists, guarding a yard nobody is trying to enter anymore, still explaining why their code is bad.
The critique can be correct and useless at the same time. I know, because I make it, and then I go home and don't launch anything.
They came for our yard. It's only fair. Let's go and take theirs. I'm trying to. Come with me.
Loading...