What Is Wrong With Software Engineers?

What I think most people don’t understand is that vibe coding was never meant to replace engineers.

It was meant to democratize the ability to create software.

For decades, people have wanted to customize their digital lives. Not just wallpapers and ringtones, but real behavior: how tools work, how information flows, how tasks are automated. The desire has always been there. What wasn’t there was access.

Developers, especially those deeply entrenched in the tech ecosystem, often underestimate how hard it was for non-technical people to build even the simplest things. If you didn’t know how to code, you were locked out. Your only option was to adapt to whatever software someone else decided you should use.

When many developers first heard about vibe coding, they imagined; optimistically or pessimistically, depending on who you ask:

1. A future where computers write software as well as traditional engineers.
2. 2. A future where developers themselves are replaced.

That fear misses the point.

What actually changed is that we’ve entered an era where people who don’t fit the traditional mold of “engineer” can now create things that were previously impossible for them. Not because they suddenly became great programmers, but because the abstraction barrier finally moved.

Someone can now build something as complex as a browser prototype, an internal tool, or a small SaaS product in days… not years. That’s not replacing engineers. That’s expanding who gets to participate.

This is where Silicon Valley is placing its bets.

Replit. Lovable. Miyu. Entire companies are being built on the belief that the future consumer won’t just use software they’ll shape it. Modify it. Own it. Software becomes closer to clay than machinery.

But here’s the uncomfortable truth: these tools still aren’t there yet.

Despite the hype, you don’t see widespread adoption from people who are genuinely non-technical. Not because they don’t want to build but because these tools still require too much mental overhead.

In other words, they’re still engineer-first products pretending to be consumer-first ones.

And this is where I think many engineers get it wrong.

They evaluate these tools by asking: “Can this replace me?” “Is the code clean?” “Is this production-ready?”

The real question should be: “Can someone who doesn’t think like an engineer still express intent and get results?”

Because the real disruption isn’t AI writing perfect code. It’s intent becoming executable.

Engineers are trained to think in systems, constraints, and edge cases. Most people are not. Most people think in outcomes: I want this button to do that. I want my life to work this way. Historically, engineers were the translators between intent and reality.

Vibe coding tools are attempting to remove that translation layer.

They’re not successful yet, but they’re early.

So what’s “wrong” with engineers isn’t that they’re obsolete. It’s that many are defending the wrong thing. The value of engineering was never exclusivity over syntax. It was problem-solving, judgment, and taste.

As software becomes more accessible, great engineers won’t disappear. They’ll move up the abstraction stack. They’ll design systems, constraints, and platforms that millions of non-engineers can safely build on top of.

The future isn’t fewer builders.

It’s more… and that should be exciting, not threatening.