214
I will send you newest post from subreddit /r/programming
AI is a Junior Dev and needs a Lead
https://www.reddit.com/r/programming/comments/1mugchx/ai_is_a_junior_dev_and_needs_a_lead/
submitted by /u/that_guy_iain (https://www.reddit.com/user/that_guy_iain)
[link] (https://getparthenon.com/blog/ai-is-a-junior-dev-and-needs-a-lead) [comments] (https://www.reddit.com/r/programming/comments/1mugchx/ai_is_a_junior_dev_and_needs_a_lead/)
JSON.stringify got faster
https://www.reddit.com/r/programming/comments/1mueqcy/jsonstringify_got_faster/
submitted by /u/Maybe-monad (https://www.reddit.com/user/Maybe-monad)
[link] (https://v8.dev/blog/json-stringify) [comments] (https://www.reddit.com/r/programming/comments/1mueqcy/jsonstringify_got_faster/)
RG Face scan (remote facescan)
https://www.reddit.com/r/programming/comments/1mudkhs/rg_face_scan_remote_facescan/
<!-- SC_OFF -->So I was wondering in the blue app when I saw a post that buying e-wallets account especially gcash. I got curious, gcash have 2 security: MPIN and Facescan, it’s impossible to log in gcash to other device without facescan. So I decided to venture deeply, after they log in your number on their device they will send you an app called “rg_facescan”. After the installation they will send you a link that will do the facescan. After the facescan then can now use your e wallet freely. I’m planning make a research about that, can you guys help me analyze this one? Link: RG Facescan: https://bdpkg.beidoupays.com/RGScanface_1.1.0.6_sign.apk Facescan link: https://pay.beidoupays.com/scanFace?phone=09551608838 Note: I sold my account to them then asked the cs to delete my account afterwards. <!-- SC_ON --> submitted by /u/no-to-marco (https://www.reddit.com/user/no-to-marco)
[link] (https://bdpkg.beidoupays.com/RGScanface_1.1.0.6_sign.apk) [comments] (https://www.reddit.com/r/programming/comments/1mudkhs/rg_face_scan_remote_facescan/)
Event Storming: 50.000 Orange Stickies Later • Alberto Brandolini
https://www.reddit.com/r/programming/comments/1mucjwh/event_storming_50000_orange_stickies_later/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/NGXl1D-KwRI) [comments] (https://www.reddit.com/r/programming/comments/1mucjwh/event_storming_50000_orange_stickies_later/)
Study of 281 MCP plugins: 72% expose high-privilege actions; 1 in 10 fully exploitable
https://www.reddit.com/r/programming/comments/1mubl8b/study_of_281_mcp_plugins_72_expose_highprivilege/
submitted by /u/tapmylap (https://www.reddit.com/user/tapmylap)
[link] (https://www.pynt.io/blog/llm-security-blogs/state-of-mcp-security) [comments] (https://www.reddit.com/r/programming/comments/1mubl8b/study_of_281_mcp_plugins_72_expose_highprivilege/)
flow-run: LLM Orchestration, Prompt Testing & Cost Monitoring
https://www.reddit.com/r/programming/comments/1muaroc/flowrun_llm_orchestration_prompt_testing_cost/
submitted by /u/Historical_Wing_9573 (https://www.reddit.com/user/Historical_Wing_9573)
[link] (https://vitaliihonchar.com/insights/flow-run-project-description) [comments] (https://www.reddit.com/r/programming/comments/1muaroc/flowrun_llm_orchestration_prompt_testing_cost/)
API Live Sync #5: File Watching
https://www.reddit.com/r/programming/comments/1mtzw34/api_live_sync_5_file_watching/
<!-- SC_OFF -->In this post, I'll walk you through how we built two critical foundation pieces: a file watching system and a collections store that understands the relationship between your code and your API tests. <!-- SC_ON --> submitted by /u/evilhighlord (https://www.reddit.com/user/evilhighlord)
[link] (https://creative-labs.hashnode.dev/api-live-sync-5-file-watching) [comments] (https://www.reddit.com/r/programming/comments/1mtzw34/api_live_sync_5_file_watching/)
Interleaving for Retrieval Augmented Generation
https://www.reddit.com/r/programming/comments/1mtv7h9/interleaving_for_retrieval_augmented_generation/
submitted by /u/_srbhr_ (https://www.reddit.com/user/_srbhr_)
[link] (https://maxirwin.com/articles/interleaving-rag/) [comments] (https://www.reddit.com/r/programming/comments/1mtv7h9/interleaving_for_retrieval_augmented_generation/)
Immutable by default: How to avoid hidden state bugs in OOP
https://www.reddit.com/r/programming/comments/1mtm2fn/immutable_by_default_how_to_avoid_hidden_state/
submitted by /u/BackEndTea (https://www.reddit.com/user/BackEndTea)
[link] (https://backendtea.com/post/immutable-by-default/) [comments] (https://www.reddit.com/r/programming/comments/1mtm2fn/immutable_by_default_how_to_avoid_hidden_state/)
Let's make a game! 307: Battlefield boundaries
https://www.reddit.com/r/programming/comments/1mtiti1/lets_make_a_game_307_battlefield_boundaries/
submitted by /u/apeloverage (https://www.reddit.com/user/apeloverage)
[link] (https://www.youtube.com/watch?v=6BqhjjAOPj8) [comments] (https://www.reddit.com/r/programming/comments/1mtiti1/lets_make_a_game_307_battlefield_boundaries/)
[link] (https://tobiasuhlig.medium.com/benchmarking-frontends-in-2025-f6bbf43b7721?source=friends_link&sk=af0f2c6745a7ca4993bc0ae60ad0ebb4) [comments] (https://www.reddit.com/r/programming/comments/1mti1m8/benchmarking_frontends_in_2025/)
Читать полностью…
LLM Testing Strategies from OpenAI, Google, Anthropic, Meta
https://www.reddit.com/r/programming/comments/1mthzzm/llm_testing_strategies_from_openai_google/
submitted by /u/AzilenTech (https://www.reddit.com/user/AzilenTech)
[link] (https://www.azilen.com/blog/llm-testing/) [comments] (https://www.reddit.com/r/programming/comments/1mthzzm/llm_testing_strategies_from_openai_google/)
Postmortem of. E-commerce site
https://www.reddit.com/r/programming/comments/1mtghmm/postmortem_of_ecommerce_site/
submitted by /u/Electrical_Gas4694 (https://www.reddit.com/user/Electrical_Gas4694)
[link] (https://tech.amwaly.com/blog/147198/postmortem-of-e-commerce-site) [comments] (https://www.reddit.com/r/programming/comments/1mtghmm/postmortem_of_ecommerce_site/)
Ubicloud: Open source alternative to AWS
https://www.reddit.com/r/programming/comments/1mtfihf/ubicloud_open_source_alternative_to_aws/
submitted by /u/Top-Associate-6276 (https://www.reddit.com/user/Top-Associate-6276)
[link] (https://github.com/ubicloud/ubicloud) [comments] (https://www.reddit.com/r/programming/comments/1mtfihf/ubicloud_open_source_alternative_to_aws/)
NUMA Is the New Network: How Per-Socket Memory Models Are Reshaping Microservice Placement
https://www.reddit.com/r/programming/comments/1mt8qjj/numa_is_the_new_network_how_persocket_memory/
<!-- SC_OFF -->Explores how Non-Uniform Memory Access (NUMA) is reshaping microservice placement. <!-- SC_ON --> submitted by /u/mqian41 (https://www.reddit.com/user/mqian41)
[link] (https://codemia.io/blog/path/NUMA-Is-the-New-Network-How-Per-Socket-Memory-Models-Are-Reshaping-Microservice-Placement) [comments] (https://www.reddit.com/r/programming/comments/1mt8qjj/numa_is_the_new_network_how_persocket_memory/)
Prime Number Grid
https://www.reddit.com/r/programming/comments/1mufl1a/prime_number_grid/
submitted by /u/sparklingsphere (https://www.reddit.com/user/sparklingsphere)
[link] (https://susam.net/primegrid.html) [comments] (https://www.reddit.com/r/programming/comments/1mufl1a/prime_number_grid/)
Scalable System Design Patterns
https://www.reddit.com/r/programming/comments/1muehza/scalable_system_design_patterns/
submitted by /u/InspectionSpirited99 (https://www.reddit.com/user/InspectionSpirited99)
[link] (https://open.substack.com/pub/betterengineers/p/scalable-system-design-patterns?r=209a75&utm_medium=ios) [comments] (https://www.reddit.com/r/programming/comments/1muehza/scalable_system_design_patterns/)
TempS3 - Making temporary file storage simple, secure, and intelligent
https://www.reddit.com/r/programming/comments/1mudb8y/temps3_making_temporary_file_storage_simple/
<!-- SC_OFF -->TempS3 is a secure CLI tool for temporary file storage on AWS S3. It features automatic file expiration, AES-256-GCM encryption, intelligent chunking for large files, and local history tracking. Cross-platform support for Windows, Linux, macOS, and Docker. Perfect for quick, secure file sharing with zero manual cleanup. Check out the GitHub repo for installation and usage details! <!-- SC_ON --> submitted by /u/LostMathematician621 (https://www.reddit.com/user/LostMathematician621)
[link] (https://github.com/killcod3/temps3) [comments] (https://www.reddit.com/r/programming/comments/1mudb8y/temps3_making_temporary_file_storage_simple/)
Fix conflicts once with git rerere (5-min lab + real story)
https://www.reddit.com/r/programming/comments/1mubx2j/fix_conflicts_once_with_git_rerere_5min_lab_real/
<!-- SC_OFF -->git rerere = Reuse Recorded Resolution. Resolve a conflict once; Git remembers and reapplies your fix on the next identical conflict. When it helps: long rebases, cherry-picks to release branches, big lint sweeps. Gotchas: it’s textual matching—review with git diff --staged. Mini-lab: git config rerere.enabled true
git config rerere.autoupdate true # create conflict, resolve once, redo merge →
# "Resolved 'file' using previous resolution." <!-- SC_ON --> submitted by /u/sshetty03 (https://www.reddit.com/user/sshetty03)
[link] (https://medium.com/stackademic/git-rerere-explained-with-examples-fix-it-once-reuse-forever-849177a289c2?sk=1614ba91837411f7472a3467bc4f2886) [comments] (https://www.reddit.com/r/programming/comments/1mubx2j/fix_conflicts_once_with_git_rerere_5min_lab_real/)
Terminal sessions you can bookmark: Building Zellij’s web client
https://www.reddit.com/r/programming/comments/1mubc0y/terminal_sessions_you_can_bookmark_building/
submitted by /u/imsnif (https://www.reddit.com/user/imsnif)
[link] (https://poor.dev/blog/building-zellij-web-terminal/) [comments] (https://www.reddit.com/r/programming/comments/1mubc0y/terminal_sessions_you_can_bookmark_building/)
Handling Mouse and Touchscreen Input Using Ebitengine (Tutorial)
https://www.reddit.com/r/programming/comments/1mu2gl8/handling_mouse_and_touchscreen_input_using/
submitted by /u/tslocum (https://www.reddit.com/user/tslocum)
[link] (https://www.youtube.com/watch?v=GHsjG0hz9_Q) [comments] (https://www.reddit.com/r/programming/comments/1mu2gl8/handling_mouse_and_touchscreen_input_using/)
Optimising for trust
https://www.reddit.com/r/programming/comments/1mtwxwk/optimising_for_trust/
submitted by /u/SwoopsFromAbove (https://www.reddit.com/user/SwoopsFromAbove)
[link] (https://tomrenner.com/posts/optimising-for-trust/) [comments] (https://www.reddit.com/r/programming/comments/1mtwxwk/optimising_for_trust/)
Day 41: How to Secure Your Node.js App Like a Pro
https://www.reddit.com/r/programming/comments/1mtpf85/day_41_how_to_secure_your_nodejs_app_like_a_pro/
submitted by /u/MysteriousEye8494 (https://www.reddit.com/user/MysteriousEye8494)
[link] (https://blog.stackademic.com/day-41-how-to-secure-your-node-js-app-like-a-pro-2663ddc85a7d) [comments] (https://www.reddit.com/r/programming/comments/1mtpf85/day_41_how_to_secure_your_nodejs_app_like_a_pro/)
Compilation Isn't Just for Programming Languages
https://www.reddit.com/r/programming/comments/1mtm0hv/compilation_isnt_just_for_programming_languages/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming) [comments] (https://www.reddit.com/r/programming/comments/1mtm0hv/compilation_isnt_just_for_programming_languages/)
Dumper App
https://www.reddit.com/r/programming/comments/1mtir04/dumper_app/
<!-- SC_OFF -->Dumper — This is a CLI utility for creating backups databases of various types (PostgreSQL, MySQL and etc.) with flexible connection and storage settings. Today the first version this app https://github.com/elkirrs/dumper There are many ideas for adding new features. I will be grateful for every advice and feedback. <!-- SC_ON --> submitted by /u/elkirrs (https://www.reddit.com/user/elkirrs)
[link] (https://github.com/elkirrs/dumper) [comments] (https://www.reddit.com/r/programming/comments/1mtir04/dumper_app/)
Benchmarking Frontends in 2025
https://www.reddit.com/r/programming/comments/1mti1m8/benchmarking_frontends_in_2025/
<!-- SC_OFF -->Hey r/programming (https://www.reddit.com/r/programming), For a while now, I've felt that our standard frontend benchmarks don't tell the whole story for the kind of complex, data-heavy apps many of us spend our days building. Core Web Vitals are great for initial load, and the popular js-framework-benchmark is useful, but it has two major limitations for testing at-scale apps: it forbids virtualization/buffered rendering, and it doesn't simulate real-world concurrent stress (e.g., a user scrolling during a heavy background task). This means we're often flying blind when it comes to the resilience of our applications. To address this, I spent the last 10 days building a new benchmarking harness from the ground up using Playwright. The goal was to create something that could provide credible, high-precision measurements of UI performance under sustained, concurrent duress. Building it was a serious engineering challenge in itself, and I wanted to share three key lessons learned: The Parallelism Trap: My first instinct was to run tests in parallel. This was a disaster. The CPU contention between maxed-out browser instances skewed the results by up to 50%. Lesson: Accurate performance benchmarking must be run serially (--workers=1). The Latency Chasm: The back-and-forth between the Node.js test runner and the browser introduced too much noise. Lesson: Measurements must be atomic. I had to wrap the entire test logic (trigger action -> wait for condition -> measure time) in a single page.evaluate() call, executing it entirely within the browser's context to eliminate test runner latency. The Polling Fallacy: Playwright's waitFor functions (like most) use long-polling, which is not precise enough for performance measurement. You can't measure a 20ms event with a 30ms polling interval. Lesson: Don't trust polling. I had to build a custom wait mechanism using a MutationObserver to stop the timer at the exact moment the DOM reached the desired state. Why do this? This project started as a response to skepticism about claims I've made regarding the performance of a worker-based UI framework I created (neo.mjs). I claimed that offloading logic from the main thread could solve major performance bottlenecks, and the community rightly asked for proof. This benchmark is that proof. The Results The most interesting test so far pits a new neo.mjs grid against the industry-leading AG Grid (in a React app). When performing heavy operations like resizing the viewport from 50 to 200 columns with 100,000 rows, the results were stark: React + AG Grid: ~3,000-5,500ms UI update time. neo.mjs: ~400ms UI update time. That's a 7-11x performance difference, depending on the browser. This isn't an indictment of AG Grid, which is a fantastic piece of engineering. It's a powerful data point showing the architectural ceiling imposed by a single-threaded paradigm. Even a best-in-class component is ultimately limited by a blocked main thread. This is an open-source project, and I'm hoping to start a conversation about how we can better measure and build for the "lived-in" web. I'd love to get your feedback on the methodology and the results. Full Article (The "Why"): https://tobiasuhlig.medium.com/benchmarking-frontends-in-2025-f6bbf43b7721?source=friends_link&sk=af0f2c6745a7ca4993bc0ae60ad0ebb4 GitHub Repo (The "How" - code, methodology, results): https://github.com/neomjs/benchmarks Live Demo (See for yourself): https://neomjs.com/dist/production/examples/grid/bigData/index.html Thanks for reading, Tobias <!-- SC_ON --> submitted by /u/TobiasUhlig (https://www.reddit.com/user/TobiasUhlig)
Sharing a personal new cryptography paradigm experiment: Dynamic Abstraction Cryptography + Kraken-GS implementation in C
https://www.reddit.com/r/programming/comments/1mtho1g/sharing_a_personal_new_cryptography_paradigm/
submitted by /u/KenBrainniks (https://www.reddit.com/user/KenBrainniks)
[link] (https://github.com/BrunoGalimi/Kraken-GS) [comments] (https://www.reddit.com/r/programming/comments/1mtho1g/sharing_a_personal_new_cryptography_paradigm/)
Content-Addressable Storage (CAS)
https://www.reddit.com/r/programming/comments/1mtg9rn/contentaddressable_storage_cas/
submitted by /u/vannam0511 (https://www.reddit.com/user/vannam0511)
[link] (https://namvdo.ai/content-addressable-storage/) [comments] (https://www.reddit.com/r/programming/comments/1mtg9rn/contentaddressable_storage_cas/)
Kanban board TUI in go
https://www.reddit.com/r/programming/comments/1mtc89w/kanban_board_tui_in_go/
<!-- SC_OFF -->A kanban board implement in go. vim like motion undo and redo. the board are based on a list of markdown files I will implement the obsidian and nelvim plugin for this little tui. I just suffer from slow workspace switching in obsidian, use tmux session to manage workspace is much smoother to me. Because I can't escape terminal workflow which make me feel pain sometimes <!-- SC_ON --> submitted by /u/Remarkable-Hunt6309 (https://www.reddit.com/user/Remarkable-Hunt6309)
[link] (https://github.com/sokinpui/kanban-tui) [comments] (https://www.reddit.com/r/programming/comments/1mtc89w/kanban_board_tui_in_go/)
Documenting Code is boring ….but it doesn’t have to be
https://www.reddit.com/r/programming/comments/1mt6zy1/documenting_code_is_boring_but_it_doesnt_have_to/
<!-- SC_OFF -->This article got me thinking about the fundamental paradox in our industry - we all desperately need good documentation, but most of us hate creating it. The piece talks about making docs “less boring” through better design and structure, but I’m more curious about the underlying problem: is the pain of writing documentation actually worth solving, or do most developers just accept it as a necessary evil? In my experience, there are roughly three camps: 1. The sufferers - Write docs because they have to, hate every minute of it 2. The skippers - Just don’t document and hope someone else deals with it later 3. The rare unicorns - Actually enjoy writing documentation (do these people exist?) What’s your honest approach? Do you: • Power through the tedium because you know it’s important? • Use any tools/automation to make it less painful? • Just… not do it unless absolutely forced? I’m particularly interested in whether people think this is a problem worth solving with better tooling, or if it’s just an inherent part of development that we need to accept. <!-- SC_ON --> submitted by /u/Ok-Ad7050 (https://www.reddit.com/user/Ok-Ad7050)
[link] (https://medium.com/steeple-product/how-to-make-documentation-less-boring-ea50fcfa56fb) [comments] (https://www.reddit.com/r/programming/comments/1mt6zy1/documenting_code_is_boring_but_it_doesnt_have_to/)