Vibe Coding: The Infrastructure Problem
My brief explorations of tools like Lovable.dev and Bolt.new revealed that they rely on traditionally-coded infrastructure like Supabase to function effectively. This suggests vibe coding's ultimate success depends on the quality and breadth of what lies beneath it.
For prototyping and simple applications, vibe coding shows promise. But for complex production systems? I remain skeptical. I'm curious about others' experiences using these tools for anything beyond basic implementations.
The path forward, as I see it, requires specialized infrastructure tools designed for specific domains. In my own work, I've developed the ChainReact.NET library with high-level abstractions that span the entire application stack (frontend, backend, business logic, etc.) for line-of-business applications. This approach could provide the foundation that vibe coding needs to become truly effective in that domain. One-size-fits-all solutions likely won't succeed. Instead, purpose-built infrastructure for different application categories offers more promise.
What do you think? How might we bridge the gap between vibe coding's lofty ambitions and production reality? Which infrastructure areas most urgently need development to make vibe coding viable?