site banner

Culture War Roundup for the week of November 9, 2026

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.

5
Jump in the discussion.

No email address required.

Is The Hackening accelerating?

I don't think it is a coincidence that Jensen Huang was forced out at about the same time as AI-powered cyberattacks become a part of everyday life. It was easy enough to look the other way as Nvidia generated trillions of dollars for US shareholders on the back of smuggling advanced chips to China through Southeast Asia. Now that we are living with the consequences, people are poking around and finding that the Chinese open-weight AI models currently being used in cyberattacks were trained on export-banned Nvidia Blackwell chips. I was not kidding when I said that Jensen could end up as the greatest traitor to America since the Rosenbergs. I believe that he personally will face criminal charges at some point. If things get bad enough, if AI cyber-conflict becomes the new Cold War, Jensen could even be executed. No one in the future will believe that we allowed this to happen in plain sight just for a few extra basis points in stock market gains.

The speculation I heard is that they just rolled out an ai powered air traffic system. And the government officially denies a cyberattack, which I think they have been willing to blame Iran for a lot of things so the fact that they deny it hints that they know what went wrong and it's not hackers.

Instead it seems more likely that vibe coding has finally come back to bite those highly comples systems that literally nobody understands.

And probably on top of the already confusing codebase half of the code in the repo right now was checked in by robots in the last 3 months

Our LLM keeps making the same mistake over and over again. It's funny to me at this point, and why I don't trust it to write more than tests.

This is c++, and we have a stream class. The stream class can give you a string representation of the data in it. When you ask for it, it gets passed by value. The LLM keeps trying to copy this data into a vector of bytes roughly like this.

bytes.insert(bytes.end(), stream.string().begin(), stream.string().end());

Did you catch it? The string returned from the second invocation of string() is a totally different object than the string() from the second invocation. And then it tries to copy from the beginning of the first string returned, to the end of the second string returned. This actually only crashes about 50% of the time when the objects are so far apart on the heap that they exceed the maximum size of a vector. And probably for other reasons too if it ever got that far.

Of course, the LLM only writes it this way approximately 50% of the time too. But still, if you've got LLM induced brainrot and don't have tip of mind encyclopedic knowledge of your codebase, that line of code doesn't look obviously wrong.

It does this even when your harness includes a line about avoiding this problem?