Vibe Coding 上线的应用会出什么问题：continuevibe 接手维护
原文标题：What breaks after you ship a vibe-coded app (and what we're doing about it)
韩国小团队 continuevibe 面向 Vibe Coding 上线的产品提供维护服务，流程为诊断问题、界定修复范围、修复代码、测试。他们访谈发现，上线后最常出问题的是登录失效、数据丢失等赶走用户的严重 bug，以及改一处坏一处、非开发者难以描述故障。
Vibe coding made building an app ridiculously fast. You describe what you want, the AI writes it, and a few days later you have something live.
We're a small team from Korea, and before building anything ourselves we interviewed people who had shipped products this way. We expected to hear about prompts and tools. Instead, almost everyone talked about what happened after launch.
What kept coming up
- Critical bugs that drive users away. Login suddenly stops working, or data disappears. These are the bugs that make real customers leave.
- Code that's scary to touch. Fixing one thing breaks something else, and you're not sure why.
- Problems that are hard to even describe. Without a developer background, it's tough to explain what's wrong, even to an AI.
Building got easier. Running and maintaining the thing didn't.
What we're doing about it
That's why we started continuevibe. We take over maintenance for products built with vibe coding:
- Diagnose the problem
- Define the scope of the fix
- Fix the code
- Test it
A question for you
If you've shipped something with vibe coding: what broke first after launch? We'd love to hear your stories in the comments.
来源：DEV Community · Vibe Coding · dev.to