2026-06-09 · Can we stop tagging every thing as vibecoding?

Transcript

Transcript. Paraphrased; sources in notes.md.

HostJune 9th, 2026. Welcome to the show. I am Daniel, joined today by Victoria, our resident product pragmatist. Victoria, I hope your week is off to a productive start.

GuestIt is, Daniel, though I am already spiraling a bit looking at today's topics. Meta-moderation, Emacs status bars, and the eternal struggle of whether engineering quality actually matters. It feels like we are touching every nerve ending of the software community today.

HostThat is exactly the point. We are pulling these stories from the community at Lobste.rs, the tech forum where these discussions happen. Let us start with the meta-moderation side of things. People are getting tired of the term vibecoding being used as a catch-all tag for AI-generated code.

GuestIt is a mess. The author’s claim is essentially that we have lost the plot. A term that started as a way to describe a specific, generative workflow has morphed into a blunt weapon for moderation. I am looking at the Lobsters thread, and you have users like theelx pointing out that some of these commits are just mathematically too large for a human to write in a single day. If you have fifty commits with thousands of lines of churn, calling that vibecoding is just a euphemism for noise.

HostIt is interesting that the Lobsters moderators have actually stepped in. A commenter named bertieb points out that the site's own guidelines now explicitly include content created without meaningful human authorship under their definition of spam.

GuestAnd that is the right move for a community, even if it is uncomfortable. If you are a user trying to find something worth reading, it does not matter if a human or a machine wrote the post. If it is five thousand lines of junk, it is not helping you. One user, addison, put it bluntly by calling the slop tag the new spam flag. I agree with that. Don’t hide behind jargon. If it is low-value, move it to the trash so the rest of us can get back to work.

HostMoving from high-level moderation to the very granular world of text editors, we have a piece about svg-line. It is a new library for Emacs, which, for those who don’t know, is a highly extensible text editor often used for programming. The author wants better status bars that work consistently across the different types of lines Emacs provides.

GuestI looked at this and my first thought was, what does this do for the person using it? The author argues that native status bars in Emacs are fragmented. They want icons, right alignment, and multi-line layouts to look the same everywhere. They are using SVG rendering to force that consistency.

HostThe performance question came up on the Lobsters thread. A user named bertieb wondered if rendering SVGs is overkill compared to text widgets and if there is a way to handle the terminal-only mode, or -nw, which stands for no-window.

GuestThe author, chiply, was honest about it. It is a GUI-only project, so if you are in a terminal, you are out of luck. Look, as someone who builds tools, if this solves a layout frustration for a power user who spends eight hours a day in their editor, it is a valid project. It is not trying to be a global standard. It is trying to make one person's workflow slightly less irritating. That is a perfectly fine reason to write software.

HostThat leads us perfectly into our final topic, which is a critique of a very common piece of engineering advice. The author argues that when people say the user doesn't care about your tech stack or your testing, they are usually just excusing low-quality work that leads to downstream failures like performance issues or security bugs.

GuestThis is the argument that always gets my blood boiling. I have heard people say the user doesn't care about the foundation of the skyscraper, they just want an office to work in. Sure, until the foundation cracks and the building closes. A user does not care about your unit tests, but they absolutely care that your feature breaks every time you push an update.

HostA Lobsters user named hc makes a nuanced point in the thread. They suggest that these slogans are not always meant to be an excuse for shipping garbage, but rather a reminder not to get lost in your own test ideology when the product itself isn't solving the problem.

GuestThat is fair, but look at what a commenter named creesch said. They noted that the people who use these phrases often don't care about the user either. They are using the user as a shield for their own desire to cut corners. If you are shipping software that is impossible to maintain, you are making it impossible to improve the product for that user later. That is a direct hit to the business. I have seen products die because they were built on a pile of technical debt that no one wanted to touch.

HostIt is a thin line between pragmatism and negligence.

GuestExactly. Pragmatism is getting the feature out the door while keeping the system stable enough to survive the next quarter. Negligence is ignoring the stability because you think it makes you look fast.

HostWell, I think that is a good place to leave it for today. Victoria, thanks for walking us through those threads.

GuestMy pleasure, Daniel. I might have to go double-check my own project status bars after reading that Emacs post, but I promise not to force SVGs on anyone.

HostI think that is for the best. Thanks again. You can find all the stories we discussed today over on Lobsters. We will be back tomorrow. See you then.