⚖️ Vibe Coding to Production: Does Product Still Need Engineering?

Originally published on LinkedIn

⚖️ Vibe Coding to Production: Does Product Still Need Engineering? ⚖️

There’s a growing belief that with AI, product managers can just “generate the code” and skip engineering. On the surface, it looks great: AI produces a feature prototype that looks right. But then reality hits: it doesn’t scale, it has bugs, it misses non-functional requirements, and it fails under load.

Why? Because code that looks right isn’t the same as code that works right.

⚡ The gap:

- AI can generate a working demo fast. - But without engineering input, critical aspects like performance, security, resilience, observability, and maintainability are overlooked. - The result: product gets what they asked for, but not what they actually need.

At the same time, many engineers assume AI can’t do the real hard work. But with an engineer at the helm—bringing good practices, architectural thinking, and awareness of non-functional requirements—AI becomes a powerful accelerator. It’s not about replacement, it’s about augmentation.

👉 A new workflow between product, AI, and engineering:

- Vibe code for exploration: Product and AI can pair to generate quick POCs. This is powerful for discovery—especially when product doesn’t yet know exactly what they want. - Engineer at the helm: Once an idea shows promise, engineering takes over. Engineers bring rigor: refactoring, scaling, adding tests, meeting non-functional requirements. - AI + product micro-PRs: For small UI tweaks or low-risk changes, product can AI-generate code. Engineering reviews the PR, just like any other contribution.

💡 Why this matters:

- Agile thrives on fast iteration. Waiting for fully detailed requirements slows us down. - Product often needs to play with an idea before it’s fully defined. - The traditional PR process was built around contributions from many—AI-assisted product contributions can fit right in, with engineering guardrails.

✅ The balance:

- Let product + AI experiment quickly. - Let engineering guide, refine, and ensure production readiness. - Keep PR reviews central: every contribution benefits from collective oversight.

🔨 My experience: I personally turned a vibe-coded massive overhaul of an existing (yes you can do it on legacy code) ecomerce website into performant, production-ready code. I leaned on AI not only for stabalizing product-facing features, but also for non-functional aspects—performance tuning, error handling, and scalability. The combination of AI’s speed and engineering oversight made it possible to deliver both fast and right.

✨ The future isn’t “AI replaces engineering.” It’s AI unlocking faster discovery, with engineering ensuring delivery. Together, they let teams ship what product wants—and what customers actually need.