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 -
Organizational frictions are real. A year ago, I'd guess I spent 60% of my time writing code, the rest spent doing organizational bullshit. Now it's something like 95% organizational bullshit, and 5% prompting and reviewing LLM-generated code.
This seems temporary to me, though. Once everyone finishes shifting to LLM coding, organizations (mega corps or startups) that minimize the organizational aspects will outcompete those that don't.
The organisational "bullshit" is what maintains a causal connection between what the end user wants and what your code does. The big idea of the Torvalds/Raymond side of the open source movement is that when hackers work for themselves or each other they can cut 90% of it out. That gets you Linux. Cutting 100% of it out gets you GNU Hurd, so be careful.
And we all know how good Linux is on desktop or at being user friendly...
Unironically Ubuntu desktop is very good these days and very user friendly. More user friendly than Windows actually, which today makes me want to tear my hair out with the ads it forces onto you and how it won't respect your registry choices as well as three dozen other serious problems.
More options
Context Copy link
More options
Context Copy link
That's a bit optimistic about the organizational stuff in a large org. E.g. make a Gantt chart for reporting to higher ups; convert your team's tickets into a new particular spreadsheet structure; write a design proposal for a system that's already done so it can be used for promo. They aren't entirely valueless because they give organizational legibility into otherwise opaque processes for decision makers, but they're not the pleasant part of software engineering.
Agreed. I will correct my comment to "The minority of the organisational bullshit that isn't pure waste is what maintains a causal connection between what the end user wants and what your code does."
Good software management (actually good management anywhere) is partly about protecting your team from the bits of organisational bullshit that don't align them - or protecting the whole organisation by keeping them out altogether if you are the founder. And it is hard because throwing the baby out with the bathwater produces a misaligned organisation.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link