Parsing integers in C
https://www.reddit.com/r/programming/comments/1oy60m0/parsing_integers_in_c/

submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://daniel.haxx.se/blog/2025/11/13/parsing-integers-in-c/) [comments] (https://www.reddit.com/r/programming/comments/1oy60m0/parsing_integers_in_c/)

VotingWorks open source election system
https://www.reddit.com/r/programming/comments/1oyb3k2/votingworks_open_source_election_system/

submitted by /u/R2_SWE2 (https://www.reddit.com/user/R2_SWE2)
[link] (https://github.com/votingworks/vxsuite) [comments] (https://www.reddit.com/r/programming/comments/1oyb3k2/votingworks_open_source_election_system/)

Lumi musical player - WPF
https://www.reddit.com/r/programming/comments/1oyeqln/lumi_musical_player_wpf/

<!-- SC_OFF -->Hello everyone, I want to share my new project that I have been working on for some time - Lumi musical player. This is a compact, beautiful music player that lets you listen to your favorite music simply by specifying the path to a folder. Features: Design. The design of this player is transparent, which makes it look beautiful in any theme on your PC, whether it's dark, light, or any custom theme - Lumi Player will look great everywhere. Convenience. For those who don't need many features and just want to listen to music with a beautiful design. Resources. Lumi Player does not require many resources or a powerful PC; it works great on any computer. Open Source. If you want to see how this player is written or suggest improvements, the code is available on GitHub. "" Technical details: Fully written in C# using WPF Open-source under the MIT license - I welcome your suggestions and improvements! The project supports modern MVVM design patterns <!-- SC_ON --> submitted by /u/Rywent (https://www.reddit.com/user/Rywent)
[link] (https://github.com/Rywent/Lumi-Player) [comments] (https://www.reddit.com/r/programming/comments/1oyeqln/lumi_musical_player_wpf/)

Lazy Skills: A Token-Efficient Approach to Dynamic Agent Capabilities
https://www.reddit.com/r/programming/comments/1oyf9h5/lazy_skills_a_tokenefficient_approach_to_dynamic/

submitted by /u/ProfessionalHyena359 (https://www.reddit.com/user/ProfessionalHyena359)
[link] (https://open.substack.com/pub/boliv/p/lazy-skills-a-token-efficient-approach?r=egj2b&utm_medium=ios) [comments] (https://www.reddit.com/r/programming/comments/1oyf9h5/lazy_skills_a_tokenefficient_approach_to_dynamic/)

A small Python CLI that deletes half of the files in a directory
https://www.reddit.com/r/programming/comments/1oyff21/a_small_python_cli_that_deletes_half_of_the_files/

<!-- SC_OFF -->A small Python CLI that eliminates half of the files in a directory randomly. I originally built it for cleaning large test folders, then realized it’s actually useful and kind of fun. <!-- SC_ON --> submitted by /u/Ok_Researcher_6962 (https://www.reddit.com/user/Ok_Researcher_6962)
[link] (https://github.com/soldatov-ss/thanos) [comments] (https://www.reddit.com/r/programming/comments/1oyff21/a_small_python_cli_that_deletes_half_of_the_files/)

How to decide a technology change
https://www.reddit.com/r/programming/comments/1oyhb8f/how_to_decide_a_technology_change/

submitted by /u/strategizeyourcareer (https://www.reddit.com/user/strategizeyourcareer)
[link] (https://strategizeyourcareer.com/p/when-to-switch-technologies) [comments] (https://www.reddit.com/r/programming/comments/1oyhb8f/how_to_decide_a_technology_change/)

Speedrunning a CPU: RISC-V in a Week
https://www.reddit.com/r/programming/comments/1oyij1s/speedrunning_a_cpu_riscv_in_a_week/

submitted by /u/Commission-Either (https://www.reddit.com/user/Commission-Either)
[link] (https://daymare.net/blogs/speedrunning-a-cpu/) [comments] (https://www.reddit.com/r/programming/comments/1oyij1s/speedrunning_a_cpu_riscv_in_a_week/)

Google releases CodeWiki for AI-based code documentation
https://www.reddit.com/r/programming/comments/1oyjaf7/google_releases_codewiki_for_aibased_code/

submitted by /u/finallyanonymous (https://www.reddit.com/user/finallyanonymous)
[link] (https://codewiki.google/) [comments] (https://www.reddit.com/r/programming/comments/1oyjaf7/google_releases_codewiki_for_aibased_code/)

Bloom filters: the niche trick behind a 16× faster API
https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/

submitted by /u/shared_ptr (https://www.reddit.com/user/shared_ptr)
[link] (https://incident.io/blog/bloom-filters) [comments] (https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/)

ELI5 explanation of the CAP Theorem
https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/

submitted by /u/trolleid (https://www.reddit.com/user/trolleid)
[link] (https://medium.com/@lukasniessen/this-is-a-super-simple-eli5-explanation-of-the-cap-theorem-5cd9e8469ab1) [comments] (https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/)

Beyond the Vector API - A Quest for a Lower Level API #JVMLS
https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/

submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=YZLVj4UVSj0) [comments] (https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/)

Running Java on iOS
https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/

<!-- SC_OFF -->Given Apple's execution restrictions, this is an interesting approach. <!-- SC_ON --> submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://www.infoq.com/news/2025/11/java-on-ios/) [comments] (https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/)

New JavaScript engine written in Rust
https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/

submitted by /u/Different-Maize1114 (https://www.reddit.com/user/Different-Maize1114)
[link] (https://github.com/Hans-Halverson/brimstone) [comments] (https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/)

His Legal Name Is One Letter—A reminder that bad validation rules hurt people
https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/

submitted by /u/grauenwolf (https://www.reddit.com/user/grauenwolf)
[link] (https://viewfromthewing.com/his-legal-name-is-one-letter-the-airline-rejects-it-and-says-just-call-yourself-aa-creating-chaos/?utm_source=fark&utm_medium=website&utm_content=link&ICID=ref_fark) [comments] (https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/)

Verity v1.0.0: A data layer that enforces server-as-truth and eliminates optimistic updates
https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/

<!-- SC_OFF -->I've been working on Verity, a framework-agnostic data layer that addresses a problem I kept running into: modern frontends blur server-owned truth-state with client-owned view-state, leading to optimistic updates, flicker, and user distrust. Core Philosophy: The server is the only source of truth Truth-state (server data) ≠ View-state (client UI concerns) Server emits directives describing what changed, not how to update the DOM Key Features: Directive-driven invalidation — server decides what needs refreshing Framework-agnostic core with adapters for Alpine, React, Vue, Svelte Multi-client synchronization via SSE Level conversion planning (derive "summary" from "full" without refetching) No optimistic updates — honest loading states instead Automatic coalescing, latest-wins guards, memory management Use Cases: Best for applications where server truth matters: real-time dashboards, multi-user tools, financial/healthcare/compliance systems, operational control rooms. Why not just use TanStack Query/Apollo? Those are excellent libraries, but they encourage optimistic updates and put invalidation logic in client code. Verity puts the server in control of the invalidation contract and refuses to lie to users about state. Examples included: The repo contains full-stack examples in multiple domains (invoice management, financial compliance, manufacturing monitoring, telehealth triage) with "baseline" versions that don't use Verity for direct comparison. Docs: https://verity.yidi.sh (https://verity.yidi.sh/) GitHub: https://github.com/YidiDev/verity License: MIT Would love to hear feedback from the community! <!-- SC_ON --> submitted by /u/yidisprei (https://www.reddit.com/user/yidisprei)
[link] (https://verity.yidi.sh/) [comments] (https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/)

EHTML — Extended HTML for Real Apps. Sharing it in case it helps someone.
https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/

<!-- SC_OFF -->Hi everyone! I’ve been working on a project called EHTML, an HTML-first approach to building dynamic pages using mostly HTML. It lets you handle things like templating, loops, conditions, data loading, reusable components, and nested forms — all without a build step or heavy JavaScript setup. I originally built it to simplify my own workflow for small apps and prototypes, but I figured others who prefer lightweight or no-build approaches might find it useful too. It runs entirely in the browser using native ES modules and custom elements, so there’s no bundler or complex tooling involved. If you enjoy working close to the browser or like experimenting with minimalistic web development, you might find it interesting. Just sharing in case it helps someone or sparks ideas. Cheers! Link: https://e-html.org/ <!-- SC_ON --> submitted by /u/gyen (https://www.reddit.com/user/gyen)
[link] (https://e-html.org/) [comments] (https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/)

Exploring Vibe Coding - Early Impressions and Practical Framework
https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/

submitted by /u/Peefy- (https://www.reddit.com/user/Peefy-)
[link] (https://uselumis.ai/blogs/exploring-vibe-coding) [comments] (https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/)

FFM - Java's new approach to interop with native code
https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/

submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://developer.ibm.com/articles/j-ffm/) [comments] (https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/)

Finding duplicated code with tools from your CS course
https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/

submitted by /u/imachug (https://www.reddit.com/user/imachug)
[link] (https://purplesyringa.moe/blog/finding-duplicated-code-with-tools-from-your-cs-course/) [comments] (https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/)

Microservices: Microliths as a resonable alternative
https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/

<!-- SC_OFF -->There are many fallacies related to Microservices people used to believe in (some still): that they improve design (architecture) on their own, just by the mere fact of a usage that they are needed because otherwise we cannot scale that they lead to simpler solutions ...and so on, many more It does not mean that they do not have their place - sometimes they do, but in the vast majority of the cases, they are neither required because of the predicted scalability needs nor because we have so many teams (like 10+, not 3 or 4) that we absolutely must separate each other on the service (process) level. But to be honest, the last argument is probably the strongest one can voice for having a few separate (micro)services: it often is objectively easier to work in parallel for multiple teams, if they all have their own service. That is where Microlits come in. They are a special kind of a (micro)service: A microlith is basically a service that is designed using the independent module design principles which avoids calls between modules/services while processing an external request. This typically requires some status and data reconciliation mechanism between services to propagate changes that affect multiple microliths. The reconciliation mechanism must be temporally decoupled from the external request processing. Having separated the processing of the external request and the communication between Microliths, we can split our monolithic application in several smaller parts without being hit by most of the distributed systems Complexity. The tradeoff is that we have to pay the price of temporally decoupled reconciliation between the Microliths. On the other hand, we do not need to deal with the problems that arise if a call to another service fails while processing an external request. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.ufried.com/blog/microservices_fallacy_10_microliths/) [comments] (https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/)

From Apache Spark to Fighting Health Insurance Denials • Holden Karau & Julian Wood
https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/

submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/qNO8U3-ZzCk?list=PLEx5khR4g7PJozVmHNpQTVrk1QRC7YaJu) [comments] (https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/)