JavaScript Closures Explained with Interactive Demos
https://www.reddit.com/r/programming/comments/1n3th8z/javanoscript_closures_explained_with_interactive/
<!-- SC_OFF -->The best analogy to understand closures is Backpack. Read More, Check out the interactive demo here (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) function exFunctionA() { const outerVariable = "I'm from the outside!"; function exFunctionB() { console.log(outerVariable); // Accesses the variable from its "backpack" } return exFunctionB; } const myClosure = exFunctionA(); // outerFunction runs and is gone... myClosure(); //...but innerFunction still has its backpack! Logs "I'm from the outside!" Think when we define any function (Function A), we define some variables inside it (lexical scope). Here we define the variable outerVariable inside Function A. Think, to remember this information, functions create a backpack and hold all these values inside it. Then again we define another function (Function B) inside our parent function (Function A). The Function B has access to the variable defined in the parent function (Function A). So now our inner function will create a backpack and hold all this information. When our outer function (Function A) executes and returns its context and lexical scope also finishes. But remember our inner function (Function B) has its own backpack, and inside the backpack it has the variable from the parent Function A (which is already executed). Now this phenomena, after the execution of parent Function A and lapsing of its lexical scope. Our inner Function B can still access the variable which was defined inside the parent Function A is called Closures. <!-- SC_ON --> submitted by /u/sanudelhi (https://www.reddit.com/user/sanudelhi)
[link] (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) [comments] (https://www.reddit.com/r/programming/comments/1n3th8z/javanoscript_closures_explained_with_interactive/)
https://www.reddit.com/r/programming/comments/1n3th8z/javanoscript_closures_explained_with_interactive/
<!-- SC_OFF -->The best analogy to understand closures is Backpack. Read More, Check out the interactive demo here (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) function exFunctionA() { const outerVariable = "I'm from the outside!"; function exFunctionB() { console.log(outerVariable); // Accesses the variable from its "backpack" } return exFunctionB; } const myClosure = exFunctionA(); // outerFunction runs and is gone... myClosure(); //...but innerFunction still has its backpack! Logs "I'm from the outside!" Think when we define any function (Function A), we define some variables inside it (lexical scope). Here we define the variable outerVariable inside Function A. Think, to remember this information, functions create a backpack and hold all these values inside it. Then again we define another function (Function B) inside our parent function (Function A). The Function B has access to the variable defined in the parent function (Function A). So now our inner function will create a backpack and hold all this information. When our outer function (Function A) executes and returns its context and lexical scope also finishes. But remember our inner function (Function B) has its own backpack, and inside the backpack it has the variable from the parent Function A (which is already executed). Now this phenomena, after the execution of parent Function A and lapsing of its lexical scope. Our inner Function B can still access the variable which was defined inside the parent Function A is called Closures. <!-- SC_ON --> submitted by /u/sanudelhi (https://www.reddit.com/user/sanudelhi)
[link] (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) [comments] (https://www.reddit.com/r/programming/comments/1n3th8z/javanoscript_closures_explained_with_interactive/)
Understanding The Scope - with interactive Demo (play and learn)
https://www.reddit.com/r/programming/comments/1n3tkhx/understanding_the_scope_with_interactive_demo/
<!-- SC_OFF -->The JavaScript uses the lexical scoping of variables. Simply the placement of the variable will determine who can access it. The access to the variable does not depend on how and when the code runs. Javanoscript determines the access of variables at compile time itself. Play and Learn (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases)Here Hierarchy of Scope In Javanoscript Global Scope This are the variables which are accessible by all functions. We define them at the outermost place in our code structure. Function Scope These are the variables which we define inside the function (With var keyword). They are only accessible inside the function and children functions in which we define the variable. Block Scope The ES6 module provides us the block scope variable. These are the variables which we define inside any pair of curly braces { }. (using keywords let and const). <!-- SC_ON --> submitted by /u/sanudelhi (https://www.reddit.com/user/sanudelhi)
[link] (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) [comments] (https://www.reddit.com/r/programming/comments/1n3tkhx/understanding_the_scope_with_interactive_demo/)
https://www.reddit.com/r/programming/comments/1n3tkhx/understanding_the_scope_with_interactive_demo/
<!-- SC_OFF -->The JavaScript uses the lexical scoping of variables. Simply the placement of the variable will determine who can access it. The access to the variable does not depend on how and when the code runs. Javanoscript determines the access of variables at compile time itself. Play and Learn (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases)Here Hierarchy of Scope In Javanoscript Global Scope This are the variables which are accessible by all functions. We define them at the outermost place in our code structure. Function Scope These are the variables which we define inside the function (With var keyword). They are only accessible inside the function and children functions in which we define the variable. Block Scope The ES6 module provides us the block scope variable. These are the variables which we define inside any pair of curly braces { }. (using keywords let and const). <!-- SC_ON --> submitted by /u/sanudelhi (https://www.reddit.com/user/sanudelhi)
[link] (https://beyondit.blog/blogs/javanoscript-closures-simplified-scope-use-cases) [comments] (https://www.reddit.com/r/programming/comments/1n3tkhx/understanding_the_scope_with_interactive_demo/)
I'm working on implementing a programming language all my own - Not Me OP
https://www.reddit.com/r/programming/comments/1n3ukwg/im_working_on_implementing_a_programming_language/
submitted by /u/JadeLuxe (https://www.reddit.com/user/JadeLuxe)
[link] (https://eli.li/to-the-surprise-of-literally-no-one-im-working-on-implementing-a-programming-language-all-my-own) [comments] (https://www.reddit.com/r/programming/comments/1n3ukwg/im_working_on_implementing_a_programming_language/)
https://www.reddit.com/r/programming/comments/1n3ukwg/im_working_on_implementing_a_programming_language/
submitted by /u/JadeLuxe (https://www.reddit.com/user/JadeLuxe)
[link] (https://eli.li/to-the-surprise-of-literally-no-one-im-working-on-implementing-a-programming-language-all-my-own) [comments] (https://www.reddit.com/r/programming/comments/1n3ukwg/im_working_on_implementing_a_programming_language/)
Bold Devlog - August Summary - Warnings, LSP & Test
https://www.reddit.com/r/programming/comments/1n3xdf6/bold_devlog_august_summary_warnings_lsp_test/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-08-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1n3xdf6/bold_devlog_august_summary_warnings_lsp_test/)
https://www.reddit.com/r/programming/comments/1n3xdf6/bold_devlog_august_summary_warnings_lsp_test/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-08-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1n3xdf6/bold_devlog_august_summary_warnings_lsp_test/)
WoW private servers C++ code review by Tariq10x
https://www.reddit.com/r/programming/comments/1n47l0k/wow_private_servers_c_code_review_by_tariq10x/
<!-- SC_OFF -->High quality deep dive on how private servers work under the hood. As someone who played on these back in the days I always wondered how they pulled it off.. <!-- SC_ON --> submitted by /u/bulltrapking (https://www.reddit.com/user/bulltrapking)
[link] (https://youtu.be/0sX-hH9NAeM) [comments] (https://www.reddit.com/r/programming/comments/1n47l0k/wow_private_servers_c_code_review_by_tariq10x/)
https://www.reddit.com/r/programming/comments/1n47l0k/wow_private_servers_c_code_review_by_tariq10x/
<!-- SC_OFF -->High quality deep dive on how private servers work under the hood. As someone who played on these back in the days I always wondered how they pulled it off.. <!-- SC_ON --> submitted by /u/bulltrapking (https://www.reddit.com/user/bulltrapking)
[link] (https://youtu.be/0sX-hH9NAeM) [comments] (https://www.reddit.com/r/programming/comments/1n47l0k/wow_private_servers_c_code_review_by_tariq10x/)
Second edition of tinyrenderer: software rendering in 500 lines of bare C++
https://www.reddit.com/r/programming/comments/1n4bxwe/second_edition_of_tinyrenderer_software_rendering/
submitted by /u/haqreu (https://www.reddit.com/user/haqreu)
[link] (https://haqr.eu/tinyrenderer/) [comments] (https://www.reddit.com/r/programming/comments/1n4bxwe/second_edition_of_tinyrenderer_software_rendering/)
https://www.reddit.com/r/programming/comments/1n4bxwe/second_edition_of_tinyrenderer_software_rendering/
submitted by /u/haqreu (https://www.reddit.com/user/haqreu)
[link] (https://haqr.eu/tinyrenderer/) [comments] (https://www.reddit.com/r/programming/comments/1n4bxwe/second_edition_of_tinyrenderer_software_rendering/)
How I Solved S3 Write Contention with a Distributed Lock Server
https://www.reddit.com/r/programming/comments/1n4lhll/how_i_solved_s3_write_contention_with_a/
<!-- SC_OFF -->Introduction When building distributed systems, it’s common to have multiple workers or services that need to write to a shared resource — like an Amazon S3 bucket. However, S3 does not provide native locking, and concurrent writes can lead to data corruption, race conditions, or unexpected results. In this article, I’ll walk you through how I solved this problem by building and deploying a distributed lock server, and how you can do the same. The Problem: Concurrent Writes to S3 Imagine you have several distributed workers, each responsible for uploading files to the same S3 bucket. If two workers try to write the same file at the same time, you risk: Data corruption or partial writes Inconsistent state Difficult-to-debug race conditions A robust solution requires a distributed lock — something that all workers can check before writing. Step 1: Evaluating Locking Strategies I considered several approaches: S3 Object Locking: Not suitable for all use cases and can be complex to manage. DynamoDB-based locks: Reliable, but adds cost and complexity. Redis or Zookeeper: Powerful, but overkill for simple lock coordination. I wanted something lightweight, language-agnostic, and easy to deploy. Step 2: Building a Distributed Lock Server I decided to build a dedicated lock server, inspired by the simplicity of Redis’ SETNX but with a RESTful HTTP API and client libraries for multiple languages. Key features: HTTP API for acquiring and releasing locks Shared secret for secure access Client SDKs for Rust, Python, and Node.js Blocking and non-blocking lock acquisition Step 3: Implementing the Lock Server I implemented the server in Rust for performance and reliability. The server exposes two endpoints: POST /acquire — Try to acquire a lock for a resource/owner POST /release — Release the lock Each request must include a shared secret for authorization. Step 4: Integrating the Client in My Workers I created lightweight client SDKs for Python and Node.js, making it easy to add distributed locking to any worker. Python Example: from lockserver_client import Lockserver Clientclient = LockserverClient(owner='worker-123', secret='your-strong-secret') if client.acquire('s3-upload-lock'): try: upload_to_s3('my-bucket', 'file.txt') finally: client.release('s3-upload-lock') Node.js Example: const { LockserverClient } = require('lockserver-client'); const client = new LockserverClient({ owner: 'worker-123', secret: 'your-strong-secret' }); await client.acquire('s3-upload-lock'); // … upload to S3 … await client.release('s3-upload-lock'); Step 5: Deploying and Testing Deployed the lockserver as a standalone service (Docker, bare metal, or cloud VM)
Configured all workers to use the same LOCKSERVER_SECRET
Verified that only one worker could write to S3 at a time for the same resource Results No more race conditions: Only one worker writes at a time.
Language-agnostic: Any worker (Rust, Python, Node.js, etc.) can participate.
Simple integration: Just a few lines of code to add distributed locking. Conclusion By introducing a distributed lock server, I was able to solve S3 write contention in a scalable, secure, and language-agnostic way. If you’re facing similar challenges, consider using or contributing to lockserver. Links: GitHub: https://github.com/benliao/lockserver Crate: https://crates.io/crates/lockserver npm: https://www.npmjs.com/package/lockserver-client Thanks for reading! If you found this helpful, feel free to star the repo or leave a comment below. <!-- SC_ON --> submitted by /u/Plastic_Clerk7250 (https://www.reddit.com/user/Plastic_Clerk7250)
https://www.reddit.com/r/programming/comments/1n4lhll/how_i_solved_s3_write_contention_with_a/
<!-- SC_OFF -->Introduction When building distributed systems, it’s common to have multiple workers or services that need to write to a shared resource — like an Amazon S3 bucket. However, S3 does not provide native locking, and concurrent writes can lead to data corruption, race conditions, or unexpected results. In this article, I’ll walk you through how I solved this problem by building and deploying a distributed lock server, and how you can do the same. The Problem: Concurrent Writes to S3 Imagine you have several distributed workers, each responsible for uploading files to the same S3 bucket. If two workers try to write the same file at the same time, you risk: Data corruption or partial writes Inconsistent state Difficult-to-debug race conditions A robust solution requires a distributed lock — something that all workers can check before writing. Step 1: Evaluating Locking Strategies I considered several approaches: S3 Object Locking: Not suitable for all use cases and can be complex to manage. DynamoDB-based locks: Reliable, but adds cost and complexity. Redis or Zookeeper: Powerful, but overkill for simple lock coordination. I wanted something lightweight, language-agnostic, and easy to deploy. Step 2: Building a Distributed Lock Server I decided to build a dedicated lock server, inspired by the simplicity of Redis’ SETNX but with a RESTful HTTP API and client libraries for multiple languages. Key features: HTTP API for acquiring and releasing locks Shared secret for secure access Client SDKs for Rust, Python, and Node.js Blocking and non-blocking lock acquisition Step 3: Implementing the Lock Server I implemented the server in Rust for performance and reliability. The server exposes two endpoints: POST /acquire — Try to acquire a lock for a resource/owner POST /release — Release the lock Each request must include a shared secret for authorization. Step 4: Integrating the Client in My Workers I created lightweight client SDKs for Python and Node.js, making it easy to add distributed locking to any worker. Python Example: from lockserver_client import Lockserver Clientclient = LockserverClient(owner='worker-123', secret='your-strong-secret') if client.acquire('s3-upload-lock'): try: upload_to_s3('my-bucket', 'file.txt') finally: client.release('s3-upload-lock') Node.js Example: const { LockserverClient } = require('lockserver-client'); const client = new LockserverClient({ owner: 'worker-123', secret: 'your-strong-secret' }); await client.acquire('s3-upload-lock'); // … upload to S3 … await client.release('s3-upload-lock'); Step 5: Deploying and Testing Deployed the lockserver as a standalone service (Docker, bare metal, or cloud VM)
Configured all workers to use the same LOCKSERVER_SECRET
Verified that only one worker could write to S3 at a time for the same resource Results No more race conditions: Only one worker writes at a time.
Language-agnostic: Any worker (Rust, Python, Node.js, etc.) can participate.
Simple integration: Just a few lines of code to add distributed locking. Conclusion By introducing a distributed lock server, I was able to solve S3 write contention in a scalable, secure, and language-agnostic way. If you’re facing similar challenges, consider using or contributing to lockserver. Links: GitHub: https://github.com/benliao/lockserver Crate: https://crates.io/crates/lockserver npm: https://www.npmjs.com/package/lockserver-client Thanks for reading! If you found this helpful, feel free to star the repo or leave a comment below. <!-- SC_ON --> submitted by /u/Plastic_Clerk7250 (https://www.reddit.com/user/Plastic_Clerk7250)
The Parallelism Mesh Zoo
https://www.reddit.com/r/programming/comments/1n4n74c/the_parallelism_mesh_zoo/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://blog.ezyang.com/2025/08/the-parallelism-mesh-zoo/) [comments] (https://www.reddit.com/r/programming/comments/1n4n74c/the_parallelism_mesh_zoo/)
https://www.reddit.com/r/programming/comments/1n4n74c/the_parallelism_mesh_zoo/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://blog.ezyang.com/2025/08/the-parallelism-mesh-zoo/) [comments] (https://www.reddit.com/r/programming/comments/1n4n74c/the_parallelism_mesh_zoo/)
Engineers turned managers/client-facing: What actually helped with the communication learning curve?
https://www.reddit.com/r/programming/comments/1n4n934/engineers_turned_managersclientfacing_what/
<!-- SC_OFF -->Hey everyone, I've been on the technical side of data space (i.e. data scientist, data engineer) who recently got promoted to a more client-facing role, and honestly, I'm struggling. My manager's feedback was that I’m “too much into technical details” and need to work on how I communicate differently to various stakeholders. The thing is, I've always been analytical and straight to the point - it's literally what made me good at technical work. But apparently that doesn't translate well to stakeholder meetings and cross-functional collaboration. I've tried some of the usual suspects (Toastmasters, generic communication courses) but they all feel like they're designed for sales people or public speakers, not engineers. The advice is either shallow (e.g. pace, filler words) or in theory (e.g. DISC framework) which doesn't really help when your brain is wired to solve problems efficiently. So I'm curious - has anyone else hit this wall? And if so, what actually helped you? I'm also working on building a solution specifically for technical professionals (because I got tired of waiting for someone else to solve this), and I'd love to get input from people who've been through this. If you've struggled with the technical-to-business communication transition, would you mind filling out a 8-question assessment? I want to make sure I'm building something that actually addresses the real challenges, not just what I think the challenges are. https://docs.google.com/forms/d/e/1FAIpQLSfIPaUjV0Okcblh4MVkxF0kPgFww2EVQdYG7_cUfxQxR-Z8WA/viewform?usp=dialog Not trying to sell anything here - genuinely want to understand if this resonates with other people and what would actually be helpful. <!-- SC_ON --> submitted by /u/BedroomSubstantial72 (https://www.reddit.com/user/BedroomSubstantial72)
[link] (https://techspeak-pro-landing.lovable.app/) [comments] (https://www.reddit.com/r/programming/comments/1n4n934/engineers_turned_managersclientfacing_what/)
https://www.reddit.com/r/programming/comments/1n4n934/engineers_turned_managersclientfacing_what/
<!-- SC_OFF -->Hey everyone, I've been on the technical side of data space (i.e. data scientist, data engineer) who recently got promoted to a more client-facing role, and honestly, I'm struggling. My manager's feedback was that I’m “too much into technical details” and need to work on how I communicate differently to various stakeholders. The thing is, I've always been analytical and straight to the point - it's literally what made me good at technical work. But apparently that doesn't translate well to stakeholder meetings and cross-functional collaboration. I've tried some of the usual suspects (Toastmasters, generic communication courses) but they all feel like they're designed for sales people or public speakers, not engineers. The advice is either shallow (e.g. pace, filler words) or in theory (e.g. DISC framework) which doesn't really help when your brain is wired to solve problems efficiently. So I'm curious - has anyone else hit this wall? And if so, what actually helped you? I'm also working on building a solution specifically for technical professionals (because I got tired of waiting for someone else to solve this), and I'd love to get input from people who've been through this. If you've struggled with the technical-to-business communication transition, would you mind filling out a 8-question assessment? I want to make sure I'm building something that actually addresses the real challenges, not just what I think the challenges are. https://docs.google.com/forms/d/e/1FAIpQLSfIPaUjV0Okcblh4MVkxF0kPgFww2EVQdYG7_cUfxQxR-Z8WA/viewform?usp=dialog Not trying to sell anything here - genuinely want to understand if this resonates with other people and what would actually be helpful. <!-- SC_ON --> submitted by /u/BedroomSubstantial72 (https://www.reddit.com/user/BedroomSubstantial72)
[link] (https://techspeak-pro-landing.lovable.app/) [comments] (https://www.reddit.com/r/programming/comments/1n4n934/engineers_turned_managersclientfacing_what/)
IntentGraph: Open-source Python library for analyzing large codebases (dependency mapping, clustering, structured outputs)
https://www.reddit.com/r/programming/comments/1n4pnga/intentgraph_opensource_python_library_for/
submitted by /u/Raytracer (https://www.reddit.com/user/Raytracer)
[link] (https://github.com/Raytracer76/IntentGraph) [comments] (https://www.reddit.com/r/programming/comments/1n4pnga/intentgraph_opensource_python_library_for/)
https://www.reddit.com/r/programming/comments/1n4pnga/intentgraph_opensource_python_library_for/
submitted by /u/Raytracer (https://www.reddit.com/user/Raytracer)
[link] (https://github.com/Raytracer76/IntentGraph) [comments] (https://www.reddit.com/r/programming/comments/1n4pnga/intentgraph_opensource_python_library_for/)
Compiler-Driven Development: Building an Elm Playground That Compiles in the Browser
https://www.reddit.com/r/programming/comments/1n4rd6t/compilerdriven_development_building_an_elm/
submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/compiler-driven-development-elm-playground/) [comments] (https://www.reddit.com/r/programming/comments/1n4rd6t/compilerdriven_development_building_an_elm/)
https://www.reddit.com/r/programming/comments/1n4rd6t/compilerdriven_development_building_an_elm/
submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/compiler-driven-development-elm-playground/) [comments] (https://www.reddit.com/r/programming/comments/1n4rd6t/compilerdriven_development_building_an_elm/)
I don’t like NumPy
https://www.reddit.com/r/programming/comments/1n4rioj/i_dont_like_numpy/
submitted by /u/Active-Fuel-49 (https://www.reddit.com/user/Active-Fuel-49)
[link] (https://dynomight.net/numpy/) [comments] (https://www.reddit.com/r/programming/comments/1n4rioj/i_dont_like_numpy/)
https://www.reddit.com/r/programming/comments/1n4rioj/i_dont_like_numpy/
submitted by /u/Active-Fuel-49 (https://www.reddit.com/user/Active-Fuel-49)
[link] (https://dynomight.net/numpy/) [comments] (https://www.reddit.com/r/programming/comments/1n4rioj/i_dont_like_numpy/)
Next.js Is Infuriating
https://www.reddit.com/r/programming/comments/1n4rpq7/nextjs_is_infuriating/
submitted by /u/Dminik (https://www.reddit.com/user/Dminik)
[link] (https://blog.meca.sh/3lxoty3shjc2z) [comments] (https://www.reddit.com/r/programming/comments/1n4rpq7/nextjs_is_infuriating/)
https://www.reddit.com/r/programming/comments/1n4rpq7/nextjs_is_infuriating/
submitted by /u/Dminik (https://www.reddit.com/user/Dminik)
[link] (https://blog.meca.sh/3lxoty3shjc2z) [comments] (https://www.reddit.com/r/programming/comments/1n4rpq7/nextjs_is_infuriating/)
Turn off Cursor, turn on your mind
https://www.reddit.com/r/programming/comments/1n4ufic/turn_off_cursor_turn_on_your_mind/
<!-- SC_OFF -->A case against agentic coding <!-- SC_ON --> submitted by /u/Low-Strawberry7579 (https://www.reddit.com/user/Low-Strawberry7579)
[link] (https://open.substack.com/pub/allvpv/p/turn-off-cursor-turn-on-your-mind?r=6ehrq6&utm_medium=ios) [comments] (https://www.reddit.com/r/programming/comments/1n4ufic/turn_off_cursor_turn_on_your_mind/)
https://www.reddit.com/r/programming/comments/1n4ufic/turn_off_cursor_turn_on_your_mind/
<!-- SC_OFF -->A case against agentic coding <!-- SC_ON --> submitted by /u/Low-Strawberry7579 (https://www.reddit.com/user/Low-Strawberry7579)
[link] (https://open.substack.com/pub/allvpv/p/turn-off-cursor-turn-on-your-mind?r=6ehrq6&utm_medium=ios) [comments] (https://www.reddit.com/r/programming/comments/1n4ufic/turn_off_cursor_turn_on_your_mind/)
Replacing a cache service with a database
https://www.reddit.com/r/programming/comments/1n4whwd/replacing_a_cache_service_with_a_database/
submitted by /u/avinassh (https://www.reddit.com/user/avinassh)
[link] (https://avi.im/blag/2025/db-cache/) [comments] (https://www.reddit.com/r/programming/comments/1n4whwd/replacing_a_cache_service_with_a_database/)
https://www.reddit.com/r/programming/comments/1n4whwd/replacing_a_cache_service_with_a_database/
submitted by /u/avinassh (https://www.reddit.com/user/avinassh)
[link] (https://avi.im/blag/2025/db-cache/) [comments] (https://www.reddit.com/r/programming/comments/1n4whwd/replacing_a_cache_service_with_a_database/)
Spacing Over Cards
https://www.reddit.com/r/programming/comments/1n4wu9v/spacing_over_cards/
<!-- SC_OFF -->This is more about design but programmers, especially indies, would benefit more from it. TL;DR: cards got overused. Often you can achieve better results by applying the proximity principle instead. The principle is, recursively, internal spacing should be no larger than external spacing. <!-- SC_ON --> submitted by /u/Odd-Tell9763 (https://www.reddit.com/user/Odd-Tell9763)
[link] (https://smagin.fyi/posts/padding-over-cards/) [comments] (https://www.reddit.com/r/programming/comments/1n4wu9v/spacing_over_cards/)
https://www.reddit.com/r/programming/comments/1n4wu9v/spacing_over_cards/
<!-- SC_OFF -->This is more about design but programmers, especially indies, would benefit more from it. TL;DR: cards got overused. Often you can achieve better results by applying the proximity principle instead. The principle is, recursively, internal spacing should be no larger than external spacing. <!-- SC_ON --> submitted by /u/Odd-Tell9763 (https://www.reddit.com/user/Odd-Tell9763)
[link] (https://smagin.fyi/posts/padding-over-cards/) [comments] (https://www.reddit.com/r/programming/comments/1n4wu9v/spacing_over_cards/)
Google is Restricting Android’s Freedom – Say Goodbye to Installing APKs?
https://www.reddit.com/r/programming/comments/1n4xbw4/google_is_restricting_androids_freedom_say/
<!-- SC_OFF -->Android’s freedom is at risk. Google plans to block APK installations from unverified sources in Android 16 (2026). This affects students, gamers, developers, and anyone who relies on apps outside the Play Store. We can’t let Android become like iOS – closed and restrictive. Sign the petition and make your voice heard! Let’s show Google that users want choice, openness, and freedom. Sign the petition to stop Google from blocking APKs and keep the choice in YOUR hands. Every signature counts! Thank you all. <!-- SC_ON --> submitted by /u/Quiet-Caramel-6614 (https://www.reddit.com/user/Quiet-Caramel-6614)
[link] (https://chng.it/bXPb8H7sz8) [comments] (https://www.reddit.com/r/programming/comments/1n4xbw4/google_is_restricting_androids_freedom_say/)
https://www.reddit.com/r/programming/comments/1n4xbw4/google_is_restricting_androids_freedom_say/
<!-- SC_OFF -->Android’s freedom is at risk. Google plans to block APK installations from unverified sources in Android 16 (2026). This affects students, gamers, developers, and anyone who relies on apps outside the Play Store. We can’t let Android become like iOS – closed and restrictive. Sign the petition and make your voice heard! Let’s show Google that users want choice, openness, and freedom. Sign the petition to stop Google from blocking APKs and keep the choice in YOUR hands. Every signature counts! Thank you all. <!-- SC_ON --> submitted by /u/Quiet-Caramel-6614 (https://www.reddit.com/user/Quiet-Caramel-6614)
[link] (https://chng.it/bXPb8H7sz8) [comments] (https://www.reddit.com/r/programming/comments/1n4xbw4/google_is_restricting_androids_freedom_say/)
How to Grow From Senior Engineer to a Lead Role
https://www.reddit.com/r/programming/comments/1n4y36v/how_to_grow_from_senior_engineer_to_a_lead_role/
submitted by /u/gregorojstersek (https://www.reddit.com/user/gregorojstersek)
[link] (https://www.youtube.com/watch?v=UK6QUS-s7fI) [comments] (https://www.reddit.com/r/programming/comments/1n4y36v/how_to_grow_from_senior_engineer_to_a_lead_role/)
https://www.reddit.com/r/programming/comments/1n4y36v/how_to_grow_from_senior_engineer_to_a_lead_role/
submitted by /u/gregorojstersek (https://www.reddit.com/user/gregorojstersek)
[link] (https://www.youtube.com/watch?v=UK6QUS-s7fI) [comments] (https://www.reddit.com/r/programming/comments/1n4y36v/how_to_grow_from_senior_engineer_to_a_lead_role/)
How is Ultrassembler so fast?
https://www.reddit.com/r/programming/comments/1n51cc2/how_is_ultrassembler_so_fast/
submitted by /u/Slammernanners (https://www.reddit.com/user/Slammernanners)
[link] (https://jghuff.com/articles/ultrassembler-so-fast/) [comments] (https://www.reddit.com/r/programming/comments/1n51cc2/how_is_ultrassembler_so_fast/)
https://www.reddit.com/r/programming/comments/1n51cc2/how_is_ultrassembler_so_fast/
submitted by /u/Slammernanners (https://www.reddit.com/user/Slammernanners)
[link] (https://jghuff.com/articles/ultrassembler-so-fast/) [comments] (https://www.reddit.com/r/programming/comments/1n51cc2/how_is_ultrassembler_so_fast/)
Tracking outbound API calls from your application: why, what worked (and what didn’t)
https://www.reddit.com/r/programming/comments/1n53dhk/tracking_outbound_api_calls_from_your_application/
submitted by /u/soap94 (https://www.reddit.com/user/soap94)
[link] (https://wcff.bearblog.dev/tracking-all-outbound-api-calls-for-on-prem-deployments/) [comments] (https://www.reddit.com/r/programming/comments/1n53dhk/tracking_outbound_api_calls_from_your_application/)
https://www.reddit.com/r/programming/comments/1n53dhk/tracking_outbound_api_calls_from_your_application/
submitted by /u/soap94 (https://www.reddit.com/user/soap94)
[link] (https://wcff.bearblog.dev/tracking-all-outbound-api-calls-for-on-prem-deployments/) [comments] (https://www.reddit.com/r/programming/comments/1n53dhk/tracking_outbound_api_calls_from_your_application/)