Reddit Programming
199 subscribers
1.22K photos
126K links
I will send you newest post from subreddit /r/programming
Download Telegram
Announcement: Temporary LLM Content Ban
https://www.reddit.com/r/programming/comments/1s9jkzi/announcement_temporary_llm_content_ban/

<!-- SC_OFF -->Hey folks, After a lot of discussion, we've decided to trial a ban of any and all content relating to LLMs. We get a lot of posts related to LLMs and typically they are not in line with what we want the subreddit to be — a place for detailed, technical learning and discourse about software engineering, driven by high quality, informative content. And unfortunately, the volume of LLM-related content easily overwhelms other topics. We also believe that, generally, the community have been indicating that, by and large, they aren't interested in this content. So, we want to see how a trial ban impacts how people use the sub. As such: While this post is stickied, for 2-4 weeks over April, we're banning all LLM-related content from the sub. That's posts, articles, videos about LLMs. We've had a ban on LLM-generated text for ages already, this doesn't change that. Note that this doesn't ban all AI related content. An article detailing how what would have traditionally been called an AI was made for Go? Totally fine. A technical breakdown of a machine learning process? Great! Just so long as it's not about LLMs. Edit: Yes, this is real, it's not an April Fool's joke. <!-- SC_ON --> submitted by /u/ChemicalRascal (https://www.reddit.com/user/ChemicalRascal)
[link] (https://www.reddit.com/r/programming/comments/1s9jkzi/announcement_temporary_llm_content_ban/) [comments] (https://www.reddit.com/r/programming/comments/1s9jkzi/announcement_temporary_llm_content_ban/)
The journey of a request in a Raft-based KV store (from client to commit)
https://www.reddit.com/r/programming/comments/1s9jn4n/the_journey_of_a_request_in_a_raftbased_kv_store/

<!-- SC_OFF -->After implementing the MIT 6.5840 distributed systems labs, I wanted to better understand what actually happens when a client sends a request to a replicated key-value store built on Raft. I wrote a short article where I follow the full path of a request:
client → leader → replication → commit → apply → response What surprised me is how quickly this “simple” flow breaks in practice: leader can change mid-request network partitions create stale leaders retries can lead to duplicate execution A lot of the complexity isn’t in Raft itself, but in making the system behave correctly under these conditions. Would be interested in feedback, especially if you’ve built something similar. <!-- SC_ON --> submitted by /u/am0123 (https://www.reddit.com/user/am0123)
[link] (https://abdellani.dev/posts/2026-04-01-the-journey-of-a-request-in-a-raft-based-kv-store/) [comments] (https://www.reddit.com/r/programming/comments/1s9jn4n/the_journey_of_a_request_in_a_raftbased_kv_store/)
You can't scale when you're dead [TigerBeetle video]
https://www.reddit.com/r/programming/comments/1s9o9ue/you_cant_scale_when_youre_dead_tigerbeetle_video/

<!-- SC_OFF -->From Monster Scale Summit ... Scale is about survivability, not just performance: a system that can't stay alive when things break can't scale at all. This talk examines the limits holding back most OLTP systems, traces database architecture through seven stages of survivability, and demonstrates a diagonal scaling approach designed to handle hundreds of billions of transactions. <!-- SC_ON --> submitted by /u/swdevtest (https://www.reddit.com/user/swdevtest)
[link] (https://www.youtube.com/watch?v=iWGB7b4ZvtU) [comments] (https://www.reddit.com/r/programming/comments/1s9o9ue/you_cant_scale_when_youre_dead_tigerbeetle_video/)
Understanding CPUs by building one in Kotlin
https://www.reddit.com/r/programming/comments/1s9r0nf/understanding_cpus_by_building_one_in_kotlin/

<!-- SC_OFF -->In order to understand how CPUs work internally I decided to build a small 16-bit CPU emulator entirely in Kotlin. It includes: A custom ISA (RISC/MIPS-inspired), Registers, Stack, Flags Instruction encoding/decoding ALU operations, branching and simple assembler I also wrote two detailed blog posts explaining the whole process step-by-step: 👉 Part 1 - Understanding how a CPU works: https://bloder.io/cpu-from-scratch-part-1 👉 Part 2 - Using Kotlin to create a CPU emulator: https://bloder.io/cpu-from-scratch-part-2 And here’s the full source code: 👉 https://github.com/bloderxd/kotlin-cpu <!-- SC_ON --> submitted by /u/_Bloder (https://www.reddit.com/user/_Bloder)
[link] (https://bloder.io/cpu-from-scratch-part-1) [comments] (https://www.reddit.com/r/programming/comments/1s9r0nf/understanding_cpus_by_building_one_in_kotlin/)
chronex - an Open-source social media scheduler
https://www.reddit.com/r/programming/comments/1sb4hwt/chronex_an_opensource_social_media_scheduler/

<!-- SC_OFF -->Over the past few weeks, I've been building a platform where users can connect their social accounts and automate content posting. So I built Chronex, an open-source alternative to paid content schedulers. Tech Stack Web/Platform: Next.js, tRPC, Drizzle, Better Auth Media Storage: Backblaze B2 Scheduling & Posting: Cloudflare Workers & Queues Github (https://github.com/prncexe/chronex) <!-- SC_ON --> submitted by /u/_Introvert_boi (https://www.reddit.com/user/_Introvert_boi)
[link] (https://chronex.princecodes.tech/) [comments] (https://www.reddit.com/r/programming/comments/1sb4hwt/chronex_an_opensource_social_media_scheduler/)