site banner

Culture War Roundup for the week of August 5, 2024

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.

8
Jump in the discussion.

No email address required.

Or here's a billion dollar idea, just turn on a goddamn windows machine locally with your patch before sending it out. This patch broke ~100% of windows machines it came across, so you just needed to have done 1 manual patch of 1 fucking machine locally to have discovered this bug.

That brought it home for me. Our IT department (a total of three people, one of whom never touches these projects) created a bug in their software and only caught it on the "trial" rollout. That caution might have saved nearly a dozen man-hours of workers waiting for them to revert the changes.

If we can get that right in a small company that barely touches software, how could a multibillion-dollar corporation that focused on security fail?

This is exactly my thought. I've been pushing for two additional tiers of production roll-outs for our software: Dark Releases and Smoke Releases. They've paid dividends for (relatively speaking) trivial solutions multiple times over. It's just such an obvious step to take.

Having enough discipline on your unit testing team to make things meaningful (I.E. not just Regex wildcard matching) seems so, so obvious too. But if you used the former approach you'd start seeing you have to fix that root cause many moons ago.

Yeah, there's situations where a bug gets past your development or test environment, and there's times where you're legitimately in too much of a hurry to test, but this is...

Like, the best spin I can give on this is that whatever safeties they did have were apparently enough to keep this from already happening earlier, when it didn't cause hundreds of millions of dollars in damage and probably a couple lives on the margins? But as much as the ratsphere jokes about the ideal rates of errors never being zero, the ideal rate of this error is so much lower than this that it's hard to compare.