How I use Jujutsu
https://www.reddit.com/r/programming/comments/1q97pqx/how_i_use_jujutsu/

submitted by /u/abhin4v (https://www.reddit.com/user/abhin4v)
[link] (https://abhinavsarkar.net/posts/jj-usage/) [comments] (https://www.reddit.com/r/programming/comments/1q97pqx/how_i_use_jujutsu/)

This Month in React 2025-12: Year in review, React2Shell (RCE, DOS, SCE, oh my)
https://www.reddit.com/r/programming/comments/1q98ixs/this_month_in_react_202512_year_in_review/

submitted by /u/vcarl (https://www.reddit.com/user/vcarl)
[link] (https://www.reactiflux.com/trannoscripts/tmir-2025-12) [comments] (https://www.reddit.com/r/programming/comments/1q98ixs/this_month_in_react_202512_year_in_review/)

Notes on Distributed Consensus and Raft
https://www.reddit.com/r/programming/comments/1q999j6/notes_on_distributed_consensus_and_raft/

submitted by /u/Helpful_Geologist430 (https://www.reddit.com/user/Helpful_Geologist430)
[link] (https://cefboud.com/posts/distributed-consensus-raft-kafka/) [comments] (https://www.reddit.com/r/programming/comments/1q999j6/notes_on_distributed_consensus_and_raft/)

Code Is Cheap Now. Software Isn’t.
https://www.reddit.com/r/programming/comments/1q9adyo/code_is_cheap_now_software_isnt/

submitted by /u/bustyLaserCannon (https://www.reddit.com/user/bustyLaserCannon)
[link] (https://www.chrisgregori.dev/opinion/code-is-cheap-now-software-isnt) [comments] (https://www.reddit.com/r/programming/comments/1q9adyo/code_is_cheap_now_software_isnt/)

Google will limit Android source releases to twice a year
https://www.reddit.com/r/programming/comments/1q9aq7j/google_will_limit_android_source_releases_to/

submitted by /u/NYPuppy (https://www.reddit.com/user/NYPuppy)
[link] (https://source.android.com/) [comments] (https://www.reddit.com/r/programming/comments/1q9aq7j/google_will_limit_android_source_releases_to/)

Vibe coding needs git blame
https://www.reddit.com/r/programming/comments/1q9cyxz/vibe_coding_needs_git_blame/

submitted by /u/jakozaur (https://www.reddit.com/user/jakozaur)
[link] (https://quesma.com/blog/vibe-code-git-blame/) [comments] (https://www.reddit.com/r/programming/comments/1q9cyxz/vibe_coding_needs_git_blame/)

flow - a keyboard first Kanban board in the terminal
https://www.reddit.com/r/programming/comments/1q9g7wp/flow_a_keyboard_first_kanban_board_in_the_terminal/

<!-- SC_OFF -->I built a small keyboard first Kanban board that runs entirely in the terminal. It focuses on fast keyboard workflows and avoiding context switching just to move work around. Runs out of the box with a demo board loaded from disk and supports local persistence. Repo: https://github.com/jsubroto/flow <!-- SC_ON --> submitted by /u/MYGRA1N (https://www.reddit.com/user/MYGRA1N)
[link] (https://github.com/jsubroto/flow) [comments] (https://www.reddit.com/r/programming/comments/1q9g7wp/flow_a_keyboard_first_kanban_board_in_the_terminal/)

chr2 - a deterministic replicated log with a durable outbox for side effects
https://www.reddit.com/r/programming/comments/1q9jc36/chr2_a_deterministic_replicated_log_with_a/

<!-- SC_OFF -->Existing consensus libraries replicate logs and elect leaders. They do not solve the part that actually breaks production systems: crash safe side effects. The moment your state machine sends an email, charges a card, or fires a webhook, you’ve stepped outside consensus. If the leader crashes after performing the side effect but before committing it, failover turns retries into duplicates unless you bolt on a second protocol. I kept re implementing that second protocol. chr2 is my attempt to make it explicit. mechanism: -deterministic apply context: application code receives block_time from the log header and a deterministic RNG seed derived from the previous hash, so replay produces identical state transitions. - crash safe WAL: entries are CRC’d, payload hashed, and hash chained. Recovery is strict, torn tails are truncated; mid-log corruption halts. - durable fencing for view changes: a manifest persists the highest view and votes using atomic tmp+fsync+rename, rejecting messages from zombie leaders after restart. - replicated outbox: side effects are stored as "pending" in replicated state. Only the leader executes them under a fencing token. Completion is recorded by committing an acknowledge event, so failover only re-executes effects that were never durably acknowledged. Trade-offs (because there always are): Side effects are intentionally at-least-once; “exactly once” requires sinks to dedupe using stable effect IDs. The system prefers halting on ambiguous disk states over guessing. Some pieces are still being tightened (e.g. persisting client request dedupe state as replicated data rather than an in memory cache). Repo: https://github.com/abokhalill/chr2 If you’ve ever had “exactly once” collapse the first time a leader died mid-flight, this problem shape will look familiar. <!-- SC_ON --> submitted by /u/AdministrativeAsk305 (https://www.reddit.com/user/AdministrativeAsk305)
[link] (https://github.com/abokhalill/chr2) [comments] (https://www.reddit.com/r/programming/comments/1q9jc36/chr2_a_deterministic_replicated_log_with_a/)

Built a real-time vessel tracker using H3 hexagonal spatial indexing for proximity detection
https://www.reddit.com/r/programming/comments/1q9jplj/built_a_realtime_vessel_tracker_using_h3/

<!-- SC_OFF -->Wrote up the full implementation here if you're interested in the technical details: https://dev-jeb.com/deliberate/portal/blog/ocean-terminal-vessel-tracker <!-- SC_ON --> submitted by /u/dev_jeb (https://www.reddit.com/user/dev_jeb)
[link] (https://dev-jeb.com/deliberate/portal/showcase/ocean-terminal-vessel-tracker) [comments] (https://www.reddit.com/r/programming/comments/1q9jplj/built_a_realtime_vessel_tracker_using_h3/)

Gixy-Next: NGINX Configuration Security & Hardening Scanner
https://www.reddit.com/r/programming/comments/1q9u4w1/gixynext_nginx_configuration_security_hardening/

submitted by /u/MegaManSec2 (https://www.reddit.com/user/MegaManSec2)
[link] (https://gixy.io/) [comments] (https://www.reddit.com/r/programming/comments/1q9u4w1/gixynext_nginx_configuration_security_hardening/)

The biggest obstacle for engineer productivity in 2026
https://www.reddit.com/r/programming/comments/1q9uiks/the_biggest_obstacle_for_engineer_productivity_in/

submitted by /u/strategizeyourcareer (https://www.reddit.com/user/strategizeyourcareer)
[link] (https://strategizeyourcareer.com/p/this-ai-problem-is-the-biggest-risk-for-software-engineers-in-2026) [comments] (https://www.reddit.com/r/programming/comments/1q9uiks/the_biggest_obstacle_for_engineer_productivity_in/)