site banner

Culture War Roundup for the week of December 19, 2022

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.

16
Jump in the discussion.

No email address required.

So far Twitter doesn't seem to have had any critical technical failures despite sacking 2/3rds of its staffing

Regarding this specifically, I think it's incredibly funny how many of the fired employees claimed this. I understand when it's a journalist thinking websites are like some kind of mechanical clock and if there is no one there to crank it every moring it will stop. It's incredible that engineers would say "yep, the system we built is such a massive pile of shit that the moment we turn away it will fall over, shatter in a billion small pieces and no one will be able to even restart it".

A truly amazing endorsement of your own work. Much like walking around with a t-shirt that says "I have a small penis", even if it's true it should be divulged on a strict need-to-know basis.

t's incredible that engineers would say "yep, the system we built is such a massive pile of shit that the moment we turn away it will fall over, shatter in a billion small pieces and no one will be able to even restart it".

A system that doesn't need you is a system that puts you of a job. The best (for you) is a system that doesn't need you but you tell everyone that it needs you badly.

Eh, as a dev eventually if no one was at the wheel some bad data condition or external change would eventually break something that only someone familiar with the code can fix in a timely manner. Especially when you're doing new development constantly things break all the time. I wasn't really willing to weigh in on either side of whether things would break. If the firings included everyone who knows how a particular system works and that system goes down for some reason, maybe some certificate goes out of date and no one can access the functional account that has sole management rights over that certificate you could see some big pain. It's possible the core platform really is so robust that you could leave it running without touching it for years but it'd be the first such application I've heard of.