Rigorous Nonsense - Readable Code is Unreadable
https://www.reddit.com/r/programming/comments/1pi0uvr/rigorous_nonsense_readable_code_is_unreadable/

submitted by /u/Xadartt (https://www.reddit.com/user/Xadartt)
[link] (https://blog.wilsonb.com/posts/2025-06-06-readable-code-is-unreadable.html) [comments] (https://www.reddit.com/r/programming/comments/1pi0uvr/rigorous_nonsense_readable_code_is_unreadable/)

10 Habits That Make You a Great Programmer
https://www.reddit.com/r/programming/comments/1pi15pa/10_habits_that_make_you_a_great_programmer/

submitted by /u/delvin0 (https://www.reddit.com/user/delvin0)
[link] (https://medium.com/gitconnected/10-habits-that-make-you-a-great-programmer-f5fd5686d80f?sk=49221a5d9e8aeef75b5afbb704762607) [comments] (https://www.reddit.com/r/programming/comments/1pi15pa/10_habits_that_make_you_a_great_programmer/)

Really fast SPSC
https://www.reddit.com/r/programming/comments/1pi4rpj/really_fast_spsc/

<!-- SC_OFF -->would love to know your thoughts! <!-- SC_ON --> submitted by /u/M3GA-10 (https://www.reddit.com/user/M3GA-10)
[link] (https://abhikja.in/blog/2025-12-07-get-in-line/) [comments] (https://www.reddit.com/r/programming/comments/1pi4rpj/really_fast_spsc/)

Improving my flutter daily-recap app via hive caching, regenerate flows, error cards, and GH actions
https://www.reddit.com/r/programming/comments/1pi7i3k/improving_my_flutter_dailyrecap_app_via_hive/

submitted by /u/Party-Tower-5475 (https://www.reddit.com/user/Party-Tower-5475)
[link] (https://pieces.app/blog/production-ready-productivity-app?utm_source=reddit&utm_medium=referral&utm_campaign=r54) [comments] (https://www.reddit.com/r/programming/comments/1pi7i3k/improving_my_flutter_dailyrecap_app_via_hive/)

2 years with Shape-Up, and why we switched back
https://www.reddit.com/r/programming/comments/1pi8thb/2_years_with_shapeup_and_why_we_switched_back/

submitted by /u/Wirbelwind (https://www.reddit.com/user/Wirbelwind)
[link] (https://scalex.dev/blog/2-years-with-shape-up/) [comments] (https://www.reddit.com/r/programming/comments/1pi8thb/2_years_with_shapeup_and_why_we_switched_back/)

How do you modernize a legacy tech stack without a complete rewrite?
https://www.reddit.com/r/programming/comments/1piasie/how_do_you_modernize_a_legacy_tech_stack_without/

<!-- SC_OFF -->As everyone warns about rewrite projects that they are set for failure, how would you modernize legacy software written with an out-of-date tech stack like Visual FoxPro or Visual Basic 6 without a complete rewrite? We have a lot of internal applications written in those tech stacks (FoxPro, VB6, ASP, etc.). Everyone seems to say that the right way to modernize these software is through the strangler fig pattern, but how would it work with these tech stacks where the new and old software can't co-exist? We are starting a migration project to migrate the largest internal application, migrating from VB6 on Windows to a web-based application backed by Go. Everyone on the team agrees that a Big Bang rollout is the only way. Curious on what you think. More background here: https://www.reddit.com/r/programming/comments/1piasie/comment/nt4spcg/ <!-- SC_ON --> submitted by /u/thana979 (https://www.reddit.com/user/thana979)
[link] (https://learn.microsoft.com/en-us/azure/architecture/patterns/strangler-fig) [comments] (https://www.reddit.com/r/programming/comments/1piasie/how_do_you_modernize_a_legacy_tech_stack_without/)

Badge System Evolution: Building From Simple to Scalable (Part 1)
https://www.reddit.com/r/programming/comments/1pic8f3/badge_system_evolution_building_from_simple_to/

submitted by /u/Namit2111 (https://www.reddit.com/user/Namit2111)
[link] (https://www.namitjain.com/blog/backend-driven-badge-system-part-1) [comments] (https://www.reddit.com/r/programming/comments/1pic8f3/badge_system_evolution_building_from_simple_to/)

Using a piece tree to implement a lazy-loading text editor, and where this idea comes from originally
https://www.reddit.com/r/programming/comments/1picg8v/using_a_piece_tree_to_implement_a_lazyloading/

<!-- SC_OFF -->I wanted my text editor to be able to load - and edit - huge files (>>1GB) instantly. It started from an idea to support editing files hosted on slow media like S3 which is a similar but different problem (RAM is not the issue unless also those files are huge). I went back to the source code of Microsoft Word 1.1 (1990) to learn a bit more on how this was used back in the days when RAM was so scarce that the program itself consumed significant amounts of your entire system's RAM (programs employed hot swapping of its own modules in those days!) Also discovered that one of the people who came up with the piece table - J Strother Moore - previously worked on the Apollo guidance computer.
The blog includes links to some historically interesting resources and explains how the piece tree helps for laziness as well as failure recovery, diffing large buffers, etc. https://noamlewis.com/blog/2025/12/09/how-fresh-loads-huge-files-fast I'm using Claude Code to accelerate coding chores - allowing me to focus on these types of problems which require deeper understanding and keep my efforts on the higher impact tasks. <!-- SC_ON --> submitted by /u/sinelaw (https://www.reddit.com/user/sinelaw)
[link] (https://noamlewis.com/blog/2025/12/09/how-fresh-loads-huge-files-fast) [comments] (https://www.reddit.com/r/programming/comments/1picg8v/using_a_piece_tree_to_implement_a_lazyloading/)

Solving the n+1 Problem in Postgres with psycopg and pydantic
https://www.reddit.com/r/programming/comments/1pidz1t/solving_the_n1_problem_in_postgres_with_psycopg/

<!-- SC_OFF -->I wrote a tutorial with code repository on writing efficient SQL queries using some of my favourite tools: Postgres and Pydantic and Pyscopg in Python. It shows how to fetch nested objects in a singe query and map them directly to Python models. <!-- SC_ON --> submitted by /u/kivarada (https://www.reddit.com/user/kivarada)
[link] (https://insidestack.it/articles/solving-the-n-1-problem-in-postgres-with-psycopg-and-pydantic) [comments] (https://www.reddit.com/r/programming/comments/1pidz1t/solving_the_n1_problem_in_postgres_with_psycopg/)

I Tried Agentic Coding and I Hate It
https://www.reddit.com/r/programming/comments/1piel63/i_tried_agentic_coding_and_i_hate_it/

submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.youtube.com/watch?v=PqkTLhjRV1s) [comments] (https://www.reddit.com/r/programming/comments/1piel63/i_tried_agentic_coding_and_i_hate_it/)

How well do you really understand C++ type deduction?
https://www.reddit.com/r/programming/comments/1pieu3k/how_well_do_you_really_understand_c_type_deduction/

<!-- SC_OFF -->I put together a quiz to test your knowledge of C++ type deduction. See what you can get right! Each example comes with an explanation, so hopefully you learn something on the way! <!-- SC_ON --> submitted by /u/volatile-int (https://www.reddit.com/user/volatile-int)
[link] (https://www.volatileint.dev/posts/auto-type-deduction-gauntlet/) [comments] (https://www.reddit.com/r/programming/comments/1pieu3k/how_well_do_you_really_understand_c_type_deduction/)

Quick reference cheatsheet for Go developers
https://www.reddit.com/r/programming/comments/1pig57o/quick_reference_cheatsheet_for_go_developers/

<!-- SC_OFF -->I recently finished building this concise cheatsheet focused on Go fundamentals and patterns. It's currently under development, and I designed it to be a quick reference for things like concurrency basics, error handling, etc. I'd love suggestions on what to add next! Check it out here: https://app.gointerview.dev/cheatsheet Let me know what you think! <!-- SC_ON --> submitted by /u/RezaSi_ (https://www.reddit.com/user/RezaSi_)
[link] (https://app.gointerview.dev/cheatsheet) [comments] (https://www.reddit.com/r/programming/comments/1pig57o/quick_reference_cheatsheet_for_go_developers/)

My favourite small hash table
https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/

submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://www.corsix.org/content/my-favourite-small-hash-table) [comments] (https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/)

Easy microservices in .NET with RabbitMQ
https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/

<!-- SC_OFF -->Tutorial for programming microservices using the RFRabbitMQRPC NuGet library in a simple way with a .NET Web API-based framework <!-- SC_ON --> submitted by /u/Last_Enthusiasm1810 (https://www.reddit.com/user/Last_Enthusiasm1810)
[link] (https://www.youtube.com/watch?v=hrU-upEMlPk) [comments] (https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/)

How I Cultivated an Open-source Platform for learning Japanese from scratch
https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/

<!-- SC_OFF -->When I first started building my own web app for grinding kanji and Japanese vocabulary, I wasn’t planning to build a serious learning platform or anything like that. I just wanted a simple, free way to practice and learn the Japanese kana (which is essentially the Japanese alphabet, though it's more accurately described as a syllabary) - something that felt as clean and addictive as Monkeytype, but for language learners. At the time, I was a student and a solo dev (and I still am). I didn’t have a marketing budget, a team or even a clear roadmap. But I did have one goal: Build the kind of learning tool I wish existed when I started learning Japanese. Fast forward a year later, and the platform now has 10k+ monthly users and almost 1k stars on GitHub. Here’s everything I learned after almost a year. 1. Build Something You Yourself Would Use First Initially, I built my app only for myself. I was frustrated with how complicated or paywalled most Japanese learning apps felt. I wanted something fast, minimalist and distraction-free. That mindset made the first version simple but focused. I didn’t chase every feature, but just focused on one thing done extremely well: Helping myself internalize the Japanese kana through repetition, feedback and flow, with the added aesthetics and customizability inspired by Monkeytype. That focus attracted other learners who wanted exactly the same thing. 2. Open Source Early, Even When It Feels “Not Ready” The first commits were honestly messy. Actually, I even exposed my project's Google Analytics API keys at one point lol. Still, putting my app on GitHub very early on changed everything. Even when the project had 0 stars on GitHub and no real contributors, open-sourcing my app still gave my productivity a much-needed boost, because I now felt "seen" and thus had to polish and update my project regularly in the case that someone would eventually see it (and decide to roast me and my code). That being said, the real breakthrough came after I started posting about my app on Reddit, Discord and other online forums. People started opening issues, suggesting improvements and even sending pull requests. Suddenly, it wasn’t my project anymore - it became our project. The community helped me shape the roadmap, catch bugs and add features I wouldn’t have thought of alone, and took my app in an amazing direction I never would've thought of myself. 3. Focus on Design and Experience, Not Just Code A lot of open-source tools look like developer experiments - especially the project my app was initially based off of, kana pro (yes, you can google "kana pro" - it's a real website, and it's very ugly). I wanted my app to feel like a polished product - something a beginner could open and instantly understand, and also appreciate the beauty of the app's minimalist, aesthetic design. That meant obsessing over: Smooth animations and feedback loops Clean typography and layout Accessibility and mobile-first design I treated UX like part of the core functionality, not an afterthought - and users notice. Of course, the design is still far from perfect, but most users praise our unique, streamlined, no-frills approach and simplicity in terms of UI. 4. Build in Public (and Be Genuine About It) I regularly shared progress on Reddit, Discord, and a few Japanese-learning communities - not as ads, but as updates from a passionate learner. Even though I got downvoted and hated on dozens of times, people still responded to my authenticity. I wasn’t selling anything. I was just sharing something I built out of love for the language and for coding. Eventually, that transparency built trust and word-of-mouth growth that no paid marketing campaign could buy. 5. Community > Marketing My app's community has been everything. They’ve built

features, written guides, designed UI ideas and helped test new builds. A few things that helped nurture that: Creating a welcoming Discord (for learners and devs) Merging community PRs very fast Giving proper credit and showcasing contributors When people feel ownership and like they are not just the users, but the active developers of the app too, they don’t just use your app - they grow and develop it with you. 6. Keep It Free, Keep It Real The project remains completely open-source and free. No paywalls, no account sign-ups, no downloads (it's a in-browser web app, not a downloadable app store app, which a lot of users liked), no “pro” tiers or ads. That’s partly ideological - but also practical. People trust projects that stay true to their purpose. Final Thoughts Building my app has taught me more about software, design, and community than any college course ever could, even as I'm still going through college. For me, it’s been one hell of a grind; a very rewarding and, at times, confusing grind, but still. If you’re thinking of starting your own open-source project, here’s my advice: Build what you need first, not what others need. Ship early. Care about design and people. Stay consistent - it's hard to describe how many countless nights I had coding in bed at night with zero feedback, zero users and zero output, and yet I kept going because I just believed that what I'm building isn't useless and people may like and come to use it eventually. And most importantly: enjoy the process. <!-- SC_ON --> submitted by /u/tentoumushy (https://www.reddit.com/user/tentoumushy)
[link] (https://github.com/lingdojo/kana-dojo) [comments] (https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/)

Driving 3D scenes in Blender with React
https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/

submitted by /u/roman01la (https://www.reddit.com/user/roman01la)
[link] (https://romanliutikov.com/blog/driving-3d-scenes-in-blender-with-react) [comments] (https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/)

Announcing ReScript 12
https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/

<!-- SC_OFF -->ReScript 12 arrives with a redesigned build toolchain, a modular runtime, and a wave of ergonomic language features. New features include: - New Build System - Improved Standard Library - Operator Improvements - Dict Literals and Dict Pattern Matching - Nested Record Types - Variant Pattern Spreads - JSX Preserve Mode - Function-Level Directives - Regex Literals - Experimental let? Syntax <!-- SC_ON --> submitted by /u/BeamMeUpBiscotti (https://www.reddit.com/user/BeamMeUpBiscotti)
[link] (https://renoscript-lang.org/blog/release-12-0-0/) [comments] (https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/)

Rust in the Linux kernel is officially here to stay
https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/

submitted by /u/NYPuppy (https://www.reddit.com/user/NYPuppy)
[link] (https://lwn.net/Articles/1049831/) [comments] (https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/)

Go 1.26 package: runtime/secret -- zeros out registers and memory after running a function run in secret mode
https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/

submitted by /u/self (https://www.reddit.com/user/self)
[link] (https://antonz.org/accepted/runtime-secret/) [comments] (https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/)

COM Like a Bomb: Rust Outlook Add-in
https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/

<!-- SC_OFF -->A short write-up on implementing a COM integration for Outlook in Rust. <!-- SC_ON --> submitted by /u/urandomd (https://www.reddit.com/user/urandomd)
[link] (https://tritium.legal/blog/outlook) [comments] (https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/)