r/programming • u/mttd • 12h ago
r/programming • u/ChemicalRascal • May 23 '26
Announcement: We've Updated The Rules, and April Is Finally Over
After temporarily banning LLM-related content over April, and asking you for feedback on that ban, we've decided to bring about an end of the temporary, I-can't-believe-it's-still-April ban on AI-related posts.
Replacing the trial rule is a new shiny rule that refers to our new shiny AI policy. In short:
Content about AI and LLMs are considered off-topic with the sole exclusion of deeply technical content about implementation.
And if you want more detail than that, go read the policy, that's what it's there for.
In addition, when writing that rule, I realized the rules weren't listed on the old.reddit.com sidebar, so that's been updated. For those of you who are seeing those rules for the first time, everything there is not new. We've been enforcing those rules as best we can for ages. You can click the link above those to get to the old.reddit rules page, with plenty of info that doesn't exactly read well when crammed into a sidebar.
r/programming • u/macrohard_certified • 21h ago
Maybe you don't need GraphQL
alexandrehtrb.github.ior/programming • u/Sushant098123 • 7h ago
Understanding RabbitMQ in Simple Terms
sushantdhiman.devr/programming • u/fagnerbrack • 21h ago
Virtual Memory: Page Tables, TLBs, and Linux Internals
blog.codingconfessions.comr/programming • u/der_gopher • 2h ago
How to secure SSH and Postgres with Warpgate
packagemain.techr/programming • u/mttd • 12h ago
Performance Characterization of SPEC CPU 2026 on AMD EPYC 9755 Processor
arxiv.orgr/programming • u/mttd • 15h ago
[PDF] Lost Bytes At The Crossroads Between User- And Kernel-Level Memory Allocation
ibr.cs.tu-bs.der/programming • u/donutloop • 7h ago
The G7 tells industry to hurry up and prep for post-quantum encryption
cyberscoop.comr/programming • u/winsletts • 1d ago
Postgres Calculations and the Ambiguity of NULL
crunchydata.comAll the ways that NULL can cause chaos in your SQL outcomes.
r/programming • u/fagnerbrack • 1d ago
Data Access Patterns That Makes Your CPU Really Angry
blog.weineng.mer/programming • u/Legitimate_Brain_544 • 13h ago
new InetSocketAddress(host, port) resolves DNS once. Kubernetes headless services hate that
gist.github.comr/programming • u/nephrenka • 2d ago
Beyond Lambdas: Raising the Abstraction Level of Functional Code
adamtornhill.substack.comr/programming • u/mmatloka • 1d ago
Apache Kafka vs Apache Iggy: A Technical Comparison
softwaremill.comr/programming • u/drmorr0 • 2d ago
Bazel's UX is really, really, really bad
blog.appliedcomputing.ior/programming • u/PastEar9661 • 2d ago
How Do HashMaps Work Under the Hood? (putting together a toy implementation in Rust to understand performance optimization, collisions, and time complexities)
medium.comHashMaps are incredibly convenient, but treating them like a magical black box can make it easy to overlook where their performance comes from.
In this article, I explain how HashMaps work using a simple implementation in Rust. I go through hash collisions and linear probing, why primary clustering hurts performance, load factors, resizing, and more.
The implementation is intentionally simplified, but it gives a good picture of what's actually happening underneath a HashMap.
Let me know your thoughts or any feedback you have!
All writing, illustrations, and code are my own. AI was used to clean up wording and catch grammatical mistakes.