{"slug": "vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual", "title": "Vibe coding increased my uptime to 99.96% or How to vibe code an app with actual users.", "summary": "A developer reports that AI-assisted \"vibe coding\" pushed an app with real users to 99.96% uptime by pairing agents with three safeguards: test-first development across unit, API, integration and browser layers; comprehensive logging that agents can read to debug and inform decisions; and parallel QA in which agents spin up app instances and clients, stage data and users, and exercise the build. For UX work, the developer records phone sessions from the start, cropped to the screen, to review what the agent saw before shipping, then returns to the logs after merging to evaluate whether the release behaved as expected.", "body_md": "1/ Vibe coding increased my uptime to 99.96% or How to vibe code an app with actual users.\n\nsounds backwards. the ai still makes mistakes but i did three things that catch errors before users do.\n\n2/ first, a test harness.\n\ntests used to be a chore. i used to add just enough tests, after the fact, to get some of the upside without incurring the tediousness of testing everything and keeping tests updated.\n\nwith ai, test driven development is effortless and essential. tests limit the mistakes the agent can make and allows you to ship with confidence. every code change writes tests first across all \"ranges\" unit, api, integration, and browser.\n\n3/ second, log everything and make sure your agents have access to the logs. if I was consulting on AI dev, this would be the first thing I would recommend. if every request, job and deploy leaves a log line, an agent can read the whole state of the app, debugging becomes instant, and decisions are informed by what actually happened, no guessing.\n\n4/ third, parallel qa.\n\nagents launch app instances and clients on demand, stage data and users, and exercise what was built.\n\n5/ if UX is involved, record it. both phone sessions get recorded from the start, cropped to the screen, so i can watch what the agent saw before anything ships.\n\n6/ after merging, back to the logs. evaluate the release, are things working as expected? did we let any bugs slip through?\n\n7/ enjoy. development has never been so much fun", "url": "https://wpnews.pro/news/vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual", "canonical_source": "https://dev.to/metamitya/vibe-coding-increased-my-uptime-to-9996-or-how-to-vibe-code-an-app-with-actual-users-2pbe", "published_at": "2026-11-12 00:40:58+00:00", "updated_at": "2026-11-12 00:50:52.640013+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "mlops"], "entities": [], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual", "markdown": "https://wpnews.pro/news/vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual.md", "text": "https://wpnews.pro/news/vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual.txt", "jsonld": "https://wpnews.pro/news/vibe-coding-increased-my-uptime-to-99-96-or-how-to-vibe-code-an-app-with-actual.jsonld"}}