AI isn’t replacing developers anytime soon. Here’s why.
AI coding agents have taken over the conversation.

Claude Code. GitHub Copilot. Cursor. Billions of dollars of hype. Mass Layoffs. All built on one bad assumption: That a developer’s job is just to write code.

Total nonsense. I’d love to automate my job away and head to the beach. But here’s the problem: Writing code is maybe 10% of what I actually do.

If you already know the problem and have broken it down clearly, AI can help. Need to write a function to detect hexagonal peaks in images? AI can nail that.

But what about:
⚙️ Designing distributed systems that won’t fall apart under load?
🧠 Optimizing algorithms to run on weak hardware?
⚡ Explaining why the autonomy stack made a strange call?
🤔 Figuring out what the real problem is in the first place?

Vibe coding won’t fix bad architecture. It won’t fix bad thinking.  It won’t open up 7 terminals to debug your ROS pipeline

It won’t optimize your DDS config. It won’t make your design transparent to your team.

And if you use it past its limits, it will slow you down. Fast. What’s the worst “vibe coding” moment you’ve seen in production? Drop it in the comments! I want to hear the horror stories.

Follow me for more inside perspectives on AI and robotics!