Seminar2250, seminar2250@awful.systems

this one is dystopian

He gave an anecdote about his niece having a hard life moment, and him sending her a personalized song made with Suno to cheer her up. “Not the best, but it took 3 minutes!” Keep in mind, this man is a practicing musician who has composed an entire symphony.

in eternal darkness, you had to choose a red-green-blue cosmic being to side with and you would fight the cosmic being of the opposite color, but if you NG+’d it three times the timelines would merge and all three cosmic beings would get obliterated

brb gotta test something

zulip added slop to their codebase a long time ago (1, 2) but now they’ve released this bullshit blog post with some choice nonsense:

I seriously considered banning LLM use for Zulip contributions. But our view is that contributors should be allowed to use modern tools in the service of producing great, reviewable work. AI-assisted work is of course subject to the same rigorous review processes we’ve always used for community contributions.

So we decided to invest in creating, refining, and enforcing a new AI use policy, which has the following key tenets:

• End-to-end human responsibility for work and the communication around it. You always need to understand, test, and explain the changes you’re proposing to make, whether or not you used an LLM as part of your process to produce them.
• Clear and concise communication about points that actually require discussion. While we allow carefully edited AI-generated PR descriptions, we’ve had to ban AI-generated chat messages in the development community as too disruptive. Manual enforcement of this policy has been rough, with far more PRs closed without review, stern warnings, and outright bans of repeat offenders than we’ve ever had to apply before. (What do you do when someone apologizes for submitting AI slop… by copy-pasting an apology from ChatGPT, including surrounding quotation marks?) We expect that next fall, automation or other major changes will be required for the PR triage process to be manageable.

The results [of using Claude] were promising (and far better than just a few months prior) — enough for us to start investing in teaching Claude Code how to self-review its work, and how to produce PRs that are easy for maintainers to review. This has largely been an AI-supported process of digesting our contributor documentation into CLAUDE.md, and iterating when we see the model struggle.

i liked zulip 😞

89.90999999…% uptime 🐐

do people just not feel shame anymore?

I would love if there were a way to filter out pro-AI companies. Nothing would make me happier than to have an interviewer tell me “we don’t allow slop here.” Instead, I have to gauge how truthful I can be. Usually, the best I can get away with is “I haven’t personally found it very useful, because I spend more time diagnosing its errors than I would have writing the code from scratch.” (But the truth is I haven’t ever used this sloppy shit. Letting a stochastic parrot speak for me is bonker balls.)

many have expectations to set up an ide day one and it start churning out patches

I just don’t understand the thought process. They must realize that this level of automation wouldn’t require anyone to hire them?