A new site at canivibecodeit.com asks the question developers now face before writing a single line: can this be vibe coded, or does it need a human at the keyboard? It pulled 8 upvotes and 4 comments on its first Hacker News appearance — small traction, but the question it poses is becoming the default starting point for new projects.
The timing tracks. Vibe coding — Andrej Karpathy’s term for building software by talking to AI instead of typing code — has moved from meme to methodology in under a year:
- Google AI Studio shipped a dedicated vibe coding page where Gemini writes UI, logic, and setup from a plain-language description
- IBM published a vibe coding explainer drawing a hard line between code generation and software engineering — one covers a single step, the other covers seven
- Full-stack builders on DEV Community tested the limits and landed on “believe the hype, just not all of it” — you can vibe code a SaaS in hours, but it’ll be a boring one
NOTE
IBM’s framing is blunt: production software needs planning, architecture, testing, security reviews, deployment, and governance. Vibe coding handles code generation — one step of that pipeline.
The shift is real. When developers ask “can I vibe code it?” before “how do I build it?”, the default starting point has moved from editor to prompt. canivibecodeit.com is live now.