This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
My favorite adhoc test for AI in the vain of Pelican on a Bike in SVG is making the LLM write a short hello world Deno program that opens a "native" message box with some text. This is usually achieved through FFI but the specific interaction between the ffi implementation in Deno/V8, the way the strings work and pointers is enough to trip most of them up, they either ignore "modern" deno 2.0 ffi syntax or get tripped up by the interplay between the native win dll's they need to load and invoke with proper string passing through the ffi interface.
Some of the more modern LLMs have been able to one shot it, but most of them need explicit reminder of the syntax or endiannes of pointers/strings.
Totally orthogonal, but FYI it's "in the vein of" - it was originally a mining analogy, since ores show up in "veins", if you're in the same vein it's implied to be a thing of similar type.
More options
Context Copy link
My personal favorite test is working with stock tickers. Since most models vaguely map tokens to 3-4 characters, and most stock tickers are under 6 characters, it's pretty easy for them to get tripped up. I've seen all the big name models fail at consistently distinguishing between VBIL and VBILX, though for some reason Gemini is particularly egregious about it. Claude sonnet had briefly gotten pretty good about it, but it's slipping in again.
More options
Context Copy link
More options
Context Copy link