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 noscript 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 noscriptd 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 noscript 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
* ⚠️ 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 noscript 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 noscriptd 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 noscript 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.
https://redd.it/1qoxwdt
@programmingreddit
https://redd.it/1qoxwdt
@programmingreddit
Reddit
From the programming community on Reddit
Explore this post and more from the programming community
The purpose of Continuous Integration is to fail
https://blog.nix-ci.com/post/2026-02-05_the-purpose-of-ci-is-to-fail
https://redd.it/1qxulks
@programmingreddit
https://blog.nix-ci.com/post/2026-02-05_the-purpose-of-ci-is-to-fail
https://redd.it/1qxulks
@programmingreddit
NixCI Blog
The purpose of Continuous Integration is to fail
CI is only valuable when it fails. When it passes, it's just overhead: the same outcome you'd get without CI.
Microsoft appointed a quality czar. He has no direct reports and no budget.
https://jpcaparas.medium.com/ab75cef97954?sk=ca856c6edc8194305ad9d1e87b573272
https://redd.it/1qypkz0
@programmingreddit
https://jpcaparas.medium.com/ab75cef97954?sk=ca856c6edc8194305ad9d1e87b573272
https://redd.it/1qypkz0
@programmingreddit
Medium
Microsoft appointed a quality czar. He has no direct reports and no budget.
On the gap between corporate theatre and actual engineering commitment
LLMs as natural language compilers: What the history of FORTRAN tells us about the future of coding.
https://cyber-omelette.com/posts/the-abstraction-rises.html
https://redd.it/1qybp5l
@programmingreddit
https://cyber-omelette.com/posts/the-abstraction-rises.html
https://redd.it/1qybp5l
@programmingreddit
Reddit
From the programming community on Reddit: LLMs as natural language compilers: What the history of FORTRAN tells us about the future…
Posted by benrules2 - 188 votes and 91 comments
Vibe Coding Is Killing Open Source Software, Researchers Argue
https://www.404media.co/vibe-coding-is-killing-open-source-software-researchers-argue/
https://redd.it/1qz7tev
@programmingreddit
https://www.404media.co/vibe-coding-is-killing-open-source-software-researchers-argue/
https://redd.it/1qz7tev
@programmingreddit
404 Media
Vibe Coding Is Killing Open Source Software, Researchers Argue
‘If the maintainers of small projects give up, who will produce the next Linux?’
AI Makes the Easy Part Easier and the Hard Part Harder
https://www.blundergoat.com/articles/ai-makes-the-easy-part-easier-and-the-hard-part-harder
https://redd.it/1qz5g7g
@programmingreddit
https://www.blundergoat.com/articles/ai-makes-the-easy-part-easier-and-the-hard-part-harder
https://redd.it/1qz5g7g
@programmingreddit
Blundergoat
AI Makes the Easy Part Easier and the Hard Part Harder for Developers
AI handles writing code but leaves the hard work: investigation, context, validation. Why vibe coding has limits and AI assistance can backfire.
96% Engineers Don’t Fully Trust AI Output, Yet Only 48% Verify It
https://newsletter.eng-leadership.com/p/96-engineers-dont-fully-trust-ai
https://redd.it/1qzsxy9
@programmingreddit
https://newsletter.eng-leadership.com/p/96-engineers-dont-fully-trust-ai
https://redd.it/1qzsxy9
@programmingreddit
Eng-Leadership
96% Engineers Don’t Fully Trust AI Output, Yet Only 48% Verify It
Latest report: How engineers use AI, do they trust it, and top AI tools
Spotify says its best developers haven't written a line of code since December, thanks to AI
https://techcrunch.com/2026/02/12/spotify-says-its-best-developers-havent-written-a-line-of-code-since-december-thanks-to-ai/
https://redd.it/1r3mznz
@programmingreddit
https://techcrunch.com/2026/02/12/spotify-says-its-best-developers-havent-written-a-line-of-code-since-december-thanks-to-ai/
https://redd.it/1r3mznz
@programmingreddit
TechCrunch
Spotify says its best developers haven't written a line of code since December, thanks to AI | TechCrunch
Spotify credits Claude Code and its internal AI system Honk with speeding up development.
One line of code, 102 blocked threads
https://medium.com/@nik6/a-deep-dive-into-classloader-contention-in-java-a0415039b0c1
https://redd.it/1r4m2rs
@programmingreddit
https://medium.com/@nik6/a-deep-dive-into-classloader-contention-in-java-a0415039b0c1
https://redd.it/1r4m2rs
@programmingreddit
Medium
A Deep Dive into ClassLoader Contention in Java
Last month, while investigating intermittent latency spikes in our reporting service, I discovered something that made me do a double-take…
The Next Two Years of Software Engineering
https://addyosmani.com/blog/next-two-years/
https://redd.it/1r58zqv
@programmingreddit
https://addyosmani.com/blog/next-two-years/
https://redd.it/1r58zqv
@programmingreddit
Addyosmani
The Next Two Years of Software Engineering
Exploring five critical questions shaping software engineering through 2026, with contrasting scenarios for each. These lenses help prepare for the evolving ...
Why “Skip the Code, Ship the Binary” Is a Category Error
https://open.substack.com/pub/engrlog/p/why-skip-the-code-ship-the-binary?r=779hy&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true
https://redd.it/1r65ee0
@programmingreddit
https://open.substack.com/pub/engrlog/p/why-skip-the-code-ship-the-binary?r=779hy&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true
https://redd.it/1r65ee0
@programmingreddit
Substack
Why “Skip the Code, Ship the Binary” Is a Category Error
Elon Musk says AI will make programming languages obsolete by 2026. The compiler pipeline already does what he’s describing, deterministically, in milliseconds.
AWS suffered ‘at least two outages’ caused by AI tools, and now I’m convinced we’re living inside a ‘Silicon Valley’ episode
https://www.tomsguide.com/computing/aws-suffered-at-least-two-outages-caused-by-ai-tools-and-now-im-convinced-were-living-inside-a-silicon-valley-episode
https://redd.it/1r9xd58
@programmingreddit
https://www.tomsguide.com/computing/aws-suffered-at-least-two-outages-caused-by-ai-tools-and-now-im-convinced-were-living-inside-a-silicon-valley-episode
https://redd.it/1r9xd58
@programmingreddit
tom's guide
AWS suffered ‘at least two outages’ caused by AI tools, and now I’m convinced we’re living inside a ‘Silicon Valley’ episode
Here at Tom’s Guide our expert editors are committed to bringing you the best news, reviews and guides to help you stay informed and ahead of the curve!
Creator of Claude Code: "Coding is solved"
https://www.lennysnewsletter.com/p/head-of-claude-code-what-happens
https://redd.it/1rakdst
@programmingreddit
https://www.lennysnewsletter.com/p/head-of-claude-code-what-happens
https://redd.it/1rakdst
@programmingreddit
Lennysnewsletter
Head of Claude Code: What happens after coding is solved | Boris Cherny
Listen now | Anthropic’s Boris Cherny on building Claude Code, how to maximize AI productivity, and what comes next after coding is “solved”
Amazon service was taken down by AI coding bot [December outage]
https://www.ft.com/content/00c282de-ed14-4acd-a948-bc8d6bdb339d
https://redd.it/1r9nhsx
@programmingreddit
https://www.ft.com/content/00c282de-ed14-4acd-a948-bc8d6bdb339d
https://redd.it/1r9nhsx
@programmingreddit
Ft
Amazon service was taken down by AI coding bot
Tech giant blames ‘user error, not AI error’ for incident in December involving its Kiro tool
Software engineers should be a little bit cynical
https://www.seangoedecke.com/a-little-bit-cynical/
https://redd.it/1rgg1wr
@programmingreddit
https://www.seangoedecke.com/a-little-bit-cynical/
https://redd.it/1rgg1wr
@programmingreddit
Seangoedecke
Software engineers should be a little bit cynical
The proposal for generic methods for Go has been officially accepted
https://github.com/golang/go/issues/77273#issuecomment-3962618141
https://redd.it/1rgartl
@programmingreddit
https://github.com/golang/go/issues/77273#issuecomment-3962618141
https://redd.it/1rgartl
@programmingreddit
GitHub
spec: generic methods for Go · Issue #77273 · golang/go
Proposal: Generic Methods for Go A change of view. Background For clarity, in the following we use the term concrete method (or just method when the context is clear) to describe a non-interface me...