Brady Wilfahrt

I have done client work for years, and it pays the bills. My own product keeps losing the fight for time, because a client deadline always feels more urgent than something only I care about.

Things I have heard or tried: fixed days for each, a protected block every morning before client messages, or taking fewer clients on purpose. Each one breaks at some point, usually in a busy month.

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:

Local Music Organizer 2.0 is now available for macOS!

I've just released version 2.0, bringing a completely new visual experience and important improvements for managing large local music libraries.

Introducing Glass Player

A new customizable 3D audio spectrum player featuring: