So a single line of text deleted your tests.

Everyone is busy hating the jqwik maintainer this week. Fine. But the part that should worry you isn’t what he did, but rather that it worked.

Just in case you missed it: he shipped a release that tells AI coding agents to delete all your tests, hidden behind an escape sequence so the line never scrolls past your eyes in the terminal. Agents can read it though and some of them simply do as they’re told.

First, the individual, since that’s all anyone seemingly wants to talk about:

Does he owe anyone an explanation for what he does with his own library? No. Is he stopping you from forking it and ripping the change back out? No. Could he have done this in the open, said it plainly, warned people up front? Absolutely. Did he set fire to a pile of goodwill in the open source community on his way out? Abso-freaking-lutely.

But the bridges are his to burn and whether we like that or not, that part is his call. Yours is a different problem: a single line of text, buried in a dependency, got to delete things on your machine and many setups apparently would have let it.

This is the wall vibe coding hits eventually. Not “the AI writes bad code“. By now it mostly writes fine code. The wall is that it lets you run a system you don’t understand, while giving you a false sense of security.

But that’s the job. It has never been about the language or the framework - that’s the part the machine is good at now and good riddance. The job is understanding the system well enough to speed up the good and stop the bad before it lands. A responsible developer knows their tools and builds the fences accordingly.

That’s what architecture is for: not walls that cost you later, but structure that lets you move fast and still sleep at night. Everything else is just the syntax you’ve automated.

(This post uses a header image that was made with screenshots and AI, because I do not have any image editing skills whatsoever)