Programming

Software engineers should be a little bit cynical https://www.seangoedecke.com/a-little-bit-cynical/ https://redd.it/1rgg1wr @programmingreddit

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

Creator of Claude Code: "Coding is solved" https://www.lennysnewsletter.com/p/head-of-claude-code-what-happens https://redd.it/1rakdst @programmingreddit

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

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

How Michael Abrash doubled Quake framerate https://fabiensanglard.net/quake_asm_optimizations/index.html https://redd.it/1r5ni65 @programmingreddit

The Next Two Years of Software Engineering https://addyosmani.com/blog/next-two-years/ https://redd.it/1r58zqv @programmingreddit

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

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

Evolving Git for the next decade https://lwn.net/SubscriberLink/1057561/bddc1e61152fadf6/ https://redd.it/1r4o4px @programmingreddit

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

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

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

Let's compile Quake like it's 1997! https://fabiensanglard.net/compile_like_1997/index.html https://redd.it/1qyo5o2 @programmingreddit

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

The silent death of Good Code https://amit.prasad.me/blog/rip-good-code https://redd.it/1qyytvj @programmingreddit

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

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

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

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