Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Being Gullible About User Feedback Can Hurt UX
https://www.reddit.com/r/programming/comments/1p1dexs/being_gullible_about_user_feedback_can_hurt_ux/

<!-- SC_OFF -->A reflection on how easily teams can be misled by user feedback, especially when comments hide embarrassment or uncertainty, and how careful observation reveals a truth that words alone never fully show <!-- SC_ON --> submitted by /u/gamunu (https://www.reddit.com/user/gamunu)
[link] (https://fastcode.io/2025/11/19/being-gullible-about-user-feedback-can-hurt-ux/) [comments] (https://www.reddit.com/r/programming/comments/1p1dexs/being_gullible_about_user_feedback_can_hurt_ux/)
A breakdown of all OAuth 2.0 authorization flows (Server-side, PKCE, Device Code, Client Credentials)
https://www.reddit.com/r/programming/comments/1p1kplp/a_breakdown_of_all_oauth_20_authorization_flows/

<!-- SC_OFF -->I put together a practical deep-dive explaining the major OAuth 2.0 flows with diagrams: Authorization Code Flow (server-side apps) PKCE Flow (SPAs + mobile apps) Client Credentials (machine-to-machine) Device Authorization Flow (TVs, consoles, IoT) The goal was to make it easier for developers to know which flow to use for which type of app and why these flows exist at all. <!-- SC_ON --> submitted by /u/sshetty03 (https://www.reddit.com/user/sshetty03)
[link] (https://medium.com/stackademic/a-developers-guide-to-oauth-2-0-workflows-web-mobile-spa-machine-to-machine-and-device-flows-2651b6479e17?sk=b89d9953f37c87573c5f579fd0b6af08) [comments] (https://www.reddit.com/r/programming/comments/1p1kplp/a_breakdown_of_all_oauth_20_authorization_flows/)
Build Your Own Key-Value Storage Engine—Week 2
https://www.reddit.com/r/programming/comments/1p19vbw/build_your_own_keyvalue_storage_engineweek_2/

<!-- SC_OFF -->Hey folks, Something I wanted to share as it may be interesting for some people there. I've been writing a series called Build Your Own Key-Value Storage Engine in collaboration with ScyllaDB. This week (2/8), we explore the foundations of LSM trees: memtable and SSTables. <!-- SC_ON --> submitted by /u/teivah (https://www.reddit.com/user/teivah)
[link] (https://read.thecoder.cafe/p/build-your-own-kv-engine-2) [comments] (https://www.reddit.com/r/programming/comments/1p19vbw/build_your_own_keyvalue_storage_engineweek_2/)
Google quietly launches a free AI coding environment — could this be the first real Cursor alternative?
https://www.reddit.com/r/programming/comments/1p1wwhy/google_quietly_launches_a_free_ai_coding/

<!-- SC_OFF -->Just spotted Google’s latest move in the AI dev space — looks like they’re quietly testing a cloud-based environment that feels a lot like Cursor, but powered by Gemini models.
Curious if anyone here has tried it yet or benchmarked it against Cursor, Windsurf, or Codeium?
I’m exploring it for real-world coding projects and would love to compare impressions. <!-- SC_ON --> submitted by /u/No_Key_3482 (https://www.reddit.com/user/No_Key_3482)
[link] (https://medium.com/lets-code-future/breaking-google-has-just-released-a-new-alternative-to-vs-code-and-cursor-called-firebase-studio-3104670034c8) [comments] (https://www.reddit.com/r/programming/comments/1p1wwhy/google_quietly_launches_a_free_ai_coding/)
Using a Zigbee Button to run any noscript
https://www.reddit.com/r/programming/comments/1p1x2au/using_a_zigbee_button_to_run_any_noscript/

<!-- SC_OFF -->Made a short video on programming a smart home button to run any noscript you want <!-- SC_ON --> submitted by /u/btb331 (https://www.reddit.com/user/btb331)
[link] (https://youtu.be/e4awmrPl990) [comments] (https://www.reddit.com/r/programming/comments/1p1x2au/using_a_zigbee_button_to_run_any_noscript/)
Builders vs. Mercenaries - two types of engineers I keep seeing. Does this make sense?
https://www.reddit.com/r/programming/comments/1p1wse8/builders_vs_mercenaries_two_types_of_engineers_i/

<!-- SC_OFF -->I have been thinking about a pattern I keep noticing in engineering teams, and I am curious if this resonates with anyone else or if I'm just making stuff up. Builders are all about the users and the problem domain. They see code as a tool to solve real problems. They'll ship something janky if it unblocks users. Ask them to optimize something that doesn't impact the user? They're not interested. Mercenaries are all about the craft. They care deeply about clean code, performance, architecture. They'll go deep on technical problems regardless of whether anyone actually needs it solved. The quality of the work matters to them independent of business impact. But I am not sure I'm framing this right. Few questions: Does this distinction actually exist or am I imagining patterns? Which type are you? Has it changed over your career? Would love to hear if anyone else sees this or if I'm way off base here. <!-- SC_ON --> submitted by /u/grandimam (https://www.reddit.com/user/grandimam)
[link] (https://news.ycombinator.com/item?id=45989643) [comments] (https://www.reddit.com/r/programming/comments/1p1wse8/builders_vs_mercenaries_two_types_of_engineers_i/)
How we make a Reactive Database Fast, Deterministic, and Still Safe
https://www.reddit.com/r/programming/comments/1p1zasd/how_we_make_a_reactive_database_fast/

<!-- SC_OFF -->One of the fun challenges in SevenDB was making emissions fully deterministic. We do that by pushing them into the state machine itself. No async “surprises,” no node deciding to emit something on its own. If the Raft log commits the command, the state machine produces the exact same emission on every node. Determinism by construction.
But this compromises speed very significantly , so what we do to get the best of both worlds is: On the durability side: a SET is considered successful only after the Raft cluster commits it—meaning it’s replicated into the in-memory WAL buffers of a quorum. Not necessarily flushed to disk when the client sees “OK.” Why keep it like this? Because we’re taking a deliberate bet that plays extremely well in practice: • Redundancy buys durability In Raft mode, your real durability is replication. Once a command is in the memory of a majority, you can lose a minority of nodes and the data is still intact. The chance of most of your cluster dying before a disk flush happens is tiny in realistic deployments. • Fsync is the throughput killer Physical disk syncs (fsync) are orders slower than memory or network replication. Forcing the leader to fsync every write would tank performance. I prototyped batching and timed windows, and they helped—but not enough to justify making fsync part of the hot path. (There is a durable flag planned: if a client appends durable to a SET, it will wait for disk flush. Still experimental.) • Disk issues shouldn’t stall a cluster If one node's storage is slow or semi-dying, synchronous fsyncs would make the whole system crawl. By relying on quorum-memory replication, the cluster stays healthy as long as most nodes are healthy. So the tradeoff is small: yes, there’s a narrow window where a simultaneous majority crash could lose in-flight commands. But the payoff is huge: predictable performance, high availability, and a deterministic state machine where emissions behave exactly the same on every node. In distributed systems, you often bet on the failure mode you’re willing to accept. This is ours.
it helped us achieve these benchmarks SevenDB benchmark — GETSET Target: localhost:7379, conns=16, workers=16, keyspace=100000, valueSize=16B, mix=GET:50/SET:50 Warmup: 5s, Duration: 30s Ops: total=3695354 success=3695354 failed=0 Throughput: 123178 ops/s Latency (ms): p50=0.111 p95=0.226 p99=0.349 max=15.663 Reactive latency (ms): p50=0.145 p95=0.358 p99=0.988 max=7.979 (interval=100ms) <!-- SC_ON --> submitted by /u/shashanksati (https://www.reddit.com/user/shashanksati)
[link] (https://github.com/sevenDatabase/SevenDB) [comments] (https://www.reddit.com/r/programming/comments/1p1zasd/how_we_make_a_reactive_database_fast/)