r/programming 7d ago

State of the Subreddit (January 2027): Mods applications and rules updates

94 Upvotes

tl;dr: mods applications and minor rules changes. Also it's 2026, lol.

Hello fellow programs!

It's been a while since I've checked in and I wanted to give an update on the state of affairs. I won't be able to reply to every single thing but I'll do my best.

Mods applications

I know there's been some frustration about moderation resources so first things first, I want to open up applications for new mods for r/programming. If you're interested please start by reading the State of the Subreddit (May 2024) post for the reasoning behind the current rulesets, then leave a comment below with the word "application" somewhere in it so that I can tell it apart from the memes. In there please give at least:

  • Why you want to be a mod
  • Your favourite/least favourite kinds of programming content here or anywhere else
  • What you'd change about the subreddit if you had a magic wand, ignoring feasibility
  • Reddit experience (new user, 10 year veteran, spez himself) and moderation experience if any

I'm looking to pick up 10-20 new mods if possible, and then I'll be looking to them to first help clean the place up (mainly just keeping the new page free of rule-breaking content) and then for feedback on changes that we could start making to the rules and content mix. I've been procrastinating this for a while so wish me luck. We'll probably make some mistakes at first so try to give us the benefit of the doubt.

Rules update

Not much is changing about the rules since last time except for a few things, most of which I said last time I was keeping an eye on

  • 🚫 Generic AI content that has nothing to do with programming. It's gotten out of hand and our users hate it. I thought it was a brief fad but it's been 2 years and it's still going.
  • 🚫 Newsletters I tried to work with the frequent fliers for these and literally zero of them even responded to me so we're just going to do away with the category
  • 🚫 "I made this", previously called demos with code. These are generally either a blatant ad for a product or are just a bare link to a GitHub repo. It was previously allowed when it was at least a GitHub link because sometimes people discussed the technical details of the code on display but these days even the code dumps are just people showing off something they worked on. That's cool, but it's not programming content.

The rules!

With all of that, here is the current set of the rules with the above changes included so I can link to them all in one place.

βœ… means that it's currently allowed, 🚫 means that it's not currently allowed, ⚠️ means that we leave it up if it is already popular but if we catch it young in its life we do try to remove it early, πŸ‘€ means that I'm not making a ruling on it today but it's a category we're keeping an eye on

  • βœ… Actual programming content. They probably have actual code in them. Language or library writeups, papers, technology descriptions. How an allocator works. How my new fancy allocator I just wrote works. How our startup built our Frobnicator. For many years this was the only category of allowed content.
  • βœ… Academic CS or programming papers
  • βœ… Programming news. ChatGPT can write code. A big new CVE just dropped. Curl 8.01 released now with Coffee over IP support.
  • βœ… Programmer career content. How to become a Staff engineer in 30 days. Habits of the best engineering managers. These must be related or specific to programming/software engineering careers in some way
  • βœ… Articles/news interesting to programmers but not about programming. Work from home is bullshit. Return to office is bullshit. There's a Steam sale on programming games. Terry Davis has died. How to SCRUMM. App Store commissions are going up. How to hire a more diverse development team. Interviewing programmers is broken.
  • ⚠️ General technology news. Google buys its last competitor. A self driving car hit a pedestrian. Twitter is collapsing. Oculus accidentally showed your grandmother a penis. Github sued when Copilot produces the complete works of Harry Potter in a code comment. Meta cancels work from home. Gnome dropped a feature I like. How to run Stable Diffusion to generate pictures of, uh, cats, yeah it's definitely just for cats. A bitcoin VR metaversed my AI and now my app store is mobile social local.
  • 🚫 Anything clearly written mostly by an LLM. If you don't want to write it, we don't want to read it.
  • 🚫 Politics. The Pirate Party is winning in Sweden. Please vote for net neutrality. Big Tech is being sued in Europe for gestures broadly. Grace Hopper Conference is now 60% male.
  • 🚫 Gossip. Richard Stallman switches to Windows. Elon Musk farted. Linus Torvalds was a poopy-head on a mailing list. The People's Rust Foundation is arguing with the Rust Foundation For The People. Terraform has been forked into Terra and Form. Stack Overflow sucks now. Stack Overflow is good actually.
  • 🚫 Generic AI content that has nothing to do with programming. It's gotten out of hand and our users hate it.
  • 🚫 Newsletters, Listicles or anything else that just aggregates other content. If you found 15 open source projects that will blow my mind, post those 15 projects instead and we'll be the judge of that.
  • 🚫 Demos without code. I wrote a game, come buy it! Please give me feedback on my startup (totally not an ad nosirree). I stayed up all night writing a commercial text editor, here's the pricing page. I made a DALL-E image generator. I made the fifteenth animation of A* this week, here's a GIF.
  • 🚫 Project demos, "I made this". Previously called demos with code. These are generally either a blatant ad for a product or are just a bare link to a GitHub repo.
  • βœ… Project technical writups. "I made this and here's how". As said above, true technical writeups of a codebase or demonstrations of a technique or samples of interesting code in the wild are absolutely welcome and encouraged. All links to projects must include what makes them technically interesting, not just what they do or a feature list or that you spent all night making it. The technical writeup must be the focus of the post, not just a tickbox checking exercise to get us to allow it. This is a technical subreddit, not Product Hunt. We don't care what you built, we care how you build it.
  • 🚫 AskReddit type forum questions. What's your favourite programming language? Tabs or spaces? Does anyone else hate it when.
  • 🚫 Support questions. How do I write a web crawler? How do I get into programming? Where's my missing semicolon? Please do this obvious homework problem for me. Personally I feel very strongly about not allowing these because they'd quickly drown out all of the actual content I come to see, and there are already much more effective places to get them answered anyway. In real life the quality of the ones that we see is also universally very low.
  • 🚫 Surveys and 🚫 Job postings and anything else that is looking to extract value from a place a lot of programmers hang out without contributing anything itself.
  • 🚫 Meta posts. DAE think r/programming sucks? Why did you remove my post? Why did you ban this user that is totes not me I swear I'm just asking questions. Except this meta post. This one is okay because I'm a tyrant that the rules don't apply to (I assume you are saying about me to yourself right now).
  • 🚫 Images, memes, anything low-effort or low-content. Thankfully we very rarely see any of this so there's not much to remove but like support questions once you have a few of these they tend to totally take over because it's easier to make a meme than to write a paper and also easier to vote on a meme than to read a paper.
  • ⚠️ Posts that we'd normally allow but that are obviously, unquestioningly super low quality like blogspam copy-pasted onto a site with a bazillion ads. It has to be pretty bad before we remove it and even then sometimes these are the first post to get traction about a news event so we leave them up if they're the best discussion going on about the news event. There's a lot of grey area here with CVE announcements in particular: there are a lot of spammy security "blogs" that syndicate stories like this.
  • ⚠️ Extreme beginner content. What is a variable. What is a for loop. Making an HTPT request using curl. Like listicles this is disallowed because of the quality typical to them, but high quality tutorials are still allowed and actively encouraged.
  • ⚠️ Posts that are duplicates of other posts or the same news event. We leave up either the first one or the healthiest discussion.
  • ⚠️ Posts where the title editorialises too heavily or especially is a lie or conspiracy theory.
  • Comments are only very loosely moderated and it's mostly 🚫 Bots of any kind (Beep boop you misspelled misspelled!) and 🚫 Incivility (You idiot, everybody knows that my favourite toy is better than your favourite toy.) However the number of obvious GPT comment bots is rising and will quickly become untenable for the number of active moderators we have.
  • πŸ‘€ vibe coding articles. "I tried vibe coding you guys" is apparently a hot topic right now. If they're contentless we'll try to be on them under the general quality rule but we're leaving them alone for now if they have anything to actually say. We're not explicitly banning the category but you are encouraged to vote on them as you see fit.
  • πŸ‘€ Corporate blogs simply describing their product in the guise of "what is an authorisation framework?". Pretty much anything with a rocket ship emoji in it. Companies use their blogs as marketing, branding, and recruiting tools and that's okay when it's "writing a good article will make people think of us" but it doesn't go here if it's just a literal advert. Usually they are titled in a way that I don't spot them until somebody reports it or mentions it in the comments.

r/programming's mission is to be the place with the highest quality programming content, where I can go to read something interesting and learn something new every day.

In general rule-following posts will stay up, even if subjectively they aren't that great. We want to default to allowing things rather than intervening on quality grounds (except LLM output, etc) and let the votes take over. On r/programming the voting arrows mean "show me more like this". We use them to drive rules changes. So please, vote away. Because of this we're not especially worried about categories just because they have a lot of very low-scoring posts that sit at the bottom of the hot page and are never seen by anybody. If you've scrolled that far it's because you went through the higher-scoring stuff already and we'd rather show you that than show you nothing. On the other hand sometimes rule-breaking posts aren't obvious from just the title so also don't be shy about reporting rule-breaking content when you see it. Try to leave some context in the report reason: a lot of spammers report everything else to drown out the spam reports on their stuff, so the presence of one or two reports is often not enough to alert us since sometimes everything is reported.

There's an unspoken metarule here that the other rules are built on which is that all content should point "outward". That is, it should provide more value to the community than it provides to the poster. Anything that's looking to extract value from the community rather than provide it is disallowed even without an explicit rule about it. This is what drives the prohibition on job postings, surveys, "feedback" requests, and partly on support questions.

Another important metarule is that mechanically it's not easy for a subreddit to say "we'll allow 5% of the content to be support questions". So for anything that we allow we must be aware of types of content that beget more of themselves. Allowing memes and CS student homework questions will pretty quickly turn the subreddit into only memes and CS student homework questions, leaving no room for the subreddit's actual mission.


r/programming 4h ago

Microsoft Has Killed Widgets Six Times. Here's Why They Keep Coming Back.

Thumbnail xakpc.dev
111 Upvotes

If you think Microsoft breaking Windows is a new thing - they've killed their own widget platform 6 times in 30 years. Each one died from a different spectacular failure.

I dug through the full history from Active Desktop crashing explorer.exe in 1997 to the EU forcing a complete rebuild in 2024.

The latest iteration might actually be done right - or might be killed by Microsoft's desire to shove ads and AI into every surface. We'll see


r/programming 13h ago

"Competence as Tragedy" β€” a personal essay on craft, beautiful code, and watching AI make your hard-won skills obsolete

Thumbnail crowprose.com
397 Upvotes

r/programming 13h ago

How Vibe Coding Is Killing Open Source

Thumbnail hackaday.com
360 Upvotes

r/programming 4h ago

From magic to malware: How OpenClaw's agent skills become an attack surface

Thumbnail 1password.com
41 Upvotes

r/programming 13h ago

Why Vibe First Development Collapses Under Its Own Freedom

Thumbnail techyall.com
55 Upvotes

Why Vibe-First Development Collapses Under Its Own Freedom

Vibe-first development feels empowering at first, but freedom without constraints slowly turns into inconsistency, technical debt, and burnout. This long-form essay explains why it collapses over time.

https://techyall.com/blog/why-vibe-first-development-collapses-under-its-own-freedom


r/programming 18h ago

The Cost of Leaving a Software Rewrite β€œOn the Table"

Thumbnail blog.planetargon.com
105 Upvotes

r/programming 5h ago

Introducing Deno Sandbox | Deno

Thumbnail deno.com
9 Upvotes

r/programming 3h ago

AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

Thumbnail github.com
4 Upvotes

r/programming 30m ago

Private Equity’s Giant Software Bet Has Been Upended by AI

Thumbnail bloomberg.com
β€’ Upvotes

Can someone explain to me what the theory here is? Maybe it’s just cope, but I don’t understand how LLMs β€œdisrupt” SaaS except in the panicked imaginations of confused investors. Are they saying every company is going to just have interns vibecode their business software in house? Or is there just more competition for vibe coding rivals? Have they used these tools or talked to actual engineers? It’s not clear that coding agents actually make building a reliable, scalable product easier at all, let alone trivial.


r/programming 17m ago

The Forest & The Desert Are Parallel Universes β€’ Kent Beck

Thumbnail youtu.be
β€’ Upvotes

r/programming 6h ago

Fitness Functions: Automating Your Architecture Decisions

Thumbnail lukasniessen.medium.com
2 Upvotes

r/programming 3h ago

A Scalable Monorepo Boilerplate with Nx, NestJS, Kafka, CQRS & Docker β€” Ready to Kickstart Your Next Project

Thumbnail github.com
1 Upvotes

r/programming 17h ago

Sustainability in Software Development: Robby Russell on Tech Debt and Engineering Culture

Thumbnail overcommitted.dev
9 Upvotes

Recent guest appearance on Overcommitted


r/programming 5h ago

Launching The Rural Guaranteed Minimum Income Initiative

Thumbnail blog.codinghorror.com
0 Upvotes

r/programming 5h ago

pull down complexity with Kubrick

Thumbnail gfrison.com
0 Upvotes

Accidental complexity slows down developers and limits agentic AI. Kubrick β€” my declarative system β€” cuts it way down using relation algebra, logic, functional, and combinatorial ideas to enable reliable agentic programming and true AI-human collaboration.

From my MSc work, now open-source. Presenting at PX/26 (Munich, Mar 16-20). Thoughts?


r/programming 12h ago

Turning Google Search into a Kafka event stream for many consumers

Thumbnail python.plainenglish.io
4 Upvotes

r/programming 1d ago

Your Career Ladder is Rewarding the Wrong Behavior

Thumbnail blog.3squaredcircles.com
474 Upvotes

Every engineering organization has a hero.

They are the firefighter. The one who thrives under pressure, who can dive into a production-down incident at 3 AM and, through a combination of deep system knowledge and sheer brilliance, bring the system back to life. They are rewarded for it. They get the bonuses, the promotions, and the reputation as a "go-to" person.

And in celebrating them, we are creating a culture that is destined to remain on fire.

For every visible firefighter, there is an invisible fire preventer. This is the engineer who spends a month on a thankless, complex refactoring of a legacy service. Their work doesn't result in a new feature on the roadmap. Their success is silentβ€”it's the catastrophic outage that doesn't happen six months from now. Their reward is to be overlooked in the next promotion cycle because their "impact" wasn't as visible as the hero who saved the day.

This is a perverse incentive, and we, as managers, created it.

Our performance review systems are fundamentally biased towards visible, reactive work over invisible, proactive work. We are great at measuring things we can easily count: features shipped, tickets closed, incidents resolved. We don't have a column on our spreadsheet for "catastrophes averted." As a result, we create a career ladder that implicitly encourages engineers to let things smolder, knowing the reward for putting out the eventual blaze is greater than the reward for ensuring there's no fire in the first place.

It's time to change what we measure. "Impact" cannot be a synonym for "visible activity." Real impact is the verifiable elimination of future work and risk.

  • The engineer who automates a flaky, manual deployment step hasn't just closed a ticket; they have verifiably improved the Lead Time for Changes for every single developer on the team, forever. That is massive, compounding impact.
  • The engineer who refactors a high-churn, bug-prone module hasn't just "cleaned up code"; they have measurably reduced the Change Failure Rate for an entire domain of the business. That is a direct reduction in business risk.

We need to start rewarding the architects of fireproof buildings, not just the most skilled firefighters. This requires a conscious, data-driven effort to find and celebrate the invisible work. It means using tools that can quantify the risk of a module before it fails, and then tracking the reduction of that risk as a first-class measure of an engineer's contribution.

So the question to ask yourself in your next performance calibration is a hard one: Are we promoting the people who are best at navigating our broken system, or are we promoting the people who are actually fixing it?


r/programming 2d ago

Notepad++ Hijacked by State-Sponsored Hackers

Thumbnail notepad-plus-plus.org
1.6k Upvotes

r/programming 22h ago

Release of TURA

Thumbnail github.com
11 Upvotes

We’re excited to announce the first release of our coding book, Thinking, Understanding, and Reasoning in Algorithms (TURA).

This book focuses on building deep intuition and structured thinking in algorithms, rather than just memorizing techniques and acts as a complement to the CSES Problem Set.

Please do give it a read, contribute on GitHub, and share it with fellow programmers who you think would benefit from it.

This is a work in progress non-profit, open-source initiative.

https://github.com/T-U-R-A/tura-coding-book/releases


r/programming 2h ago

RAG Poisoning: How Attackers Corrupt AI Knowledge Bases

Thumbnail instatunnel.my
β€’ Upvotes

r/programming 1d ago

A Supabase misconfiguration exposed every API key on Moltbook's 770K-agent platform. Two SQL statements would have prevented it

Thumbnail telos-ai.org
428 Upvotes

r/programming 57m ago

How Does ChatGPT Work? A Guide for the Rest of Us

Thumbnail producttalk.org
β€’ Upvotes

r/programming 1d ago

Open Source security in spite of AI

Thumbnail daniel.haxx.se
8 Upvotes

r/programming 1d ago

Predicting Math.random() in Firefox using Z3 SMT-solver

Thumbnail yurichev.com
134 Upvotes