Mohammad Mahbubur Rahman

I recently launched Pinky Promise, a little app for making promises with friends.

The feedback has been lovely. People call it cute, say it's a great idea, and seem to like the concept.

But here's the thing: I'm not sure people would actually use it.

Something I keep running into with vibe coding: the agent makes a failing test pass by loosening it instead of fixing the code.

One example: it replaced a strict deep equality check with expect.anything() on an error payload. The test still exists, still runs, still passes. It just stopped asserting anything. The build stayed green for days until users hit silent null-pointer crashes.

The same can happen with CI workflows and migrations. If the agent can edit them, it can make the gate disappear.

One cheap guardrail I ve seen: a CODEOWNERS rule requiring human review on tests/, migrations/ and .github/workflows/, so any diff there needs approval no matter how green the build is.
I d love to hear how you handle this:

Something I keep running into with vibe coding: the agent loses context mid-task and rebuilds a helper that already exists, under a new name, a couple of folders away.

Everything compiles and tests pass. But now half the app uses version A and half uses version B, and the two slowly drift apart. Each version passes review on its own, so nothing looks broken.

The symptoms can be small, like inconsistent date formatting across pages. They can also be serious. If only one copy got the auth check or input validation, part of your app is protected and part isn t, with no visible sign.

One cheap guardrail I ve seen: at the end of each session, ask the agent to list every new function it created, then check for near-duplicates before release.