site banner

Culture War Roundup for the week of February 23, 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.

4
Jump in the discussion.

No email address required.

Setup a GitHub repo and sling whatever code you have already developed at it. Then writeup a 1000 or so word guide on how you did everything.

If only this were true. I’ve never had an interviewer ask about my open source work in a way that indicates they clicked through the links in my resume and read the well formatted READMEs on the projects I maintain. When I do interviews, the rubrics I’m supposed to work towards don’t have any way to include an assessment of open source work, and other members of hiring committees have never known what I’m talking about when I bring up a candidates open source work. The general sentiment seems to be that evaluating open source work is unfair to people who’ve done their work in corporate environments. I’m sure there are some hiring managers in some companies who can and do use it as a signal, but the degree to which it is ignored in standard tech companies is a huge blackpill. It’s not terrible advice because it can’t hurt, it’s just not the magic foot in the door some people hope it would be. There’s no magic key if you’re early career, especially these days. I feel bad for the youngsters.

Your networking advice sounds good, but I find it exhausting and I know a lot of great hackers do to (not claiming to be one of them). Building your personal brand is probably great for your career, but I want to write code, not win instagram to get a job. Like I probably could get more ROI by writing a blog post every five patches, but I barely have the energy to write patches, so I definitely don’t have the energy to blog and tweet about it.

I’ve never had an interviewer ask about my open source work Other members of hiring committees have never known what I’m talking about when I bring up a candidates open source work.

These sound like companies that will fail

but the degree to which it is ignored in standard tech companies is a huge blackpill.

The dude who wrote OpenClawd literally got hired by OpenAI less than a month later.

Like I probably could get more ROI by writing a blog post every five patches, but I barely have the energy to write patches, so I definitely don’t have the energy to blog and tweet about it.

Sounds like you should change careers.


I'm being pretty harsh on purpose.

"The job market isn't what I want it to be." Correct. You can either adapt to it or try something else. Complaining alone gets a person nowhere. It's an old redpill quote, so take it for what it's worth, but the saying goes "Life never gets easier, but you can get better."

Technical hiring has been fucked in one form or another since the easy money days of 08 - 16 (roughly). The people who succeed are the people who don't follow the herd and make an effort. If all you want is to resume spam that's fine - expect resume spam level results.

If you, instead, build a network, build a brand (also - who said anything about Instagram? Some of the biggest voices in tech still run their own personal text heavy blogs. Gwern comes to mind). If you don't want to do either of those things, I'm not sure what to tell you.

These sound like companies that will fail

All have been well established and successful to varying degrees. I’ve observed this pattern at FAANG, at unicorns, at established enterprise shops, basically everywhere. The only place that seemed to engage with my open source work was a very early stage startup, so maybe it helps there but for the vast majority of tech jobs it just doesn’t matter.

The dude who wrote OpenClawd literally got hired by OpenAI less than a month later.

Just write a virially successful project with enormous buzz bro. It’s a totally viable career path for average devs to become the Twitter main character for a week and land a job!

Obviously this will work for some people, but that doesn’t mean it will for most.

Sounds like you should change careers.

I’ll hang onto the gig where I get overpaid to write fun little programs until it gets automated away, thanks though. I was talking about barely having the energy to do extra unpaid work for fun on open source stuff. That I do it at all means I’m in the top few percent of professional devs passion wise. Open source work is not normal, and if you think it is you must be way out of touch with most of the industry.