Reddit Programming – Telegram
Reddit Programming
212 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Using git as a memory layer for AI code assistants
https://www.reddit.com/r/programming/comments/1n30oo9/using_git_as_a_memory_layer_for_ai_code_assistants/

<!-- SC_OFF -->Hey everyone, I've been exploring an interesting pattern: using git as a queryable memory for AI coding assistants. The problem: AI assistants like Claude have no memory between sessions and every debugging session means re-explaining your entire codebase burning lot of tokens. My approach: Auto-commit every file save to a parallel local hidden git repository, then expose git operations to the AI via MCP. Instead of feeding Claude my entire codebase, it now runs git commands directly on this hidden repo (which contains the full evolution of my codebase). The interesting part is that AI already speaks git fluently. It knows exactly which commands to run for different scenarios. Tradeoffs I'm seeing: - Pros: Massive token reduction, AI can trace bug introduction, perfect undo history - Cons: Disk usage (~12MB per 10k commits), another process running in background Has anyone else tried giving AI assistants access to version control? Thank you!
Alessandro <!-- SC_ON --> submitted by /u/Apart-Employment-592 (https://www.reddit.com/user/Apart-Employment-592)
[link] (https://github.com/blade47/shadowgit-mcp) [comments] (https://www.reddit.com/r/programming/comments/1n30oo9/using_git_as_a_memory_layer_for_ai_code_assistants/)
Self-Healing Systems: Architectural Patterns
https://www.reddit.com/r/programming/comments/1n39yxo/selfhealing_systems_architectural_patterns/

<!-- SC_OFF -->Every self-healing system operates on three core principles that work in continuous loops: Detection: The System's Nervous System Modern self-healing relies on multi-layered health signals rather than simple ping checks. Netflix's microservices don't just monitor CPU and memory—they track business metrics like recommendation accuracy and user engagement rates. Circuit Breaker Integration: When a service's error rate crosses 50%, circuit breakers automatically isolate it while healing mechanisms activate. This prevents cascade failures during recovery. Behavioral Anomaly Detection: Systems learn normal patterns and detect deviations. A sudden 300% increase in database query time triggers healing before users notice slowness. Decision: The Healing Brain The decision engine determines the appropriate response based on failure type, system state, and historical success rates of different recovery strategies. Recovery Strategy Selection: Memory leaks trigger instance replacement, while network issues trigger retry with exponential backoff. Database connection exhaustion triggers connection pool scaling. Risk Assessment: Before taking action, the system evaluates potential impact. Restarting a critical service during peak hours might cause more damage than the original problem. Action: The Healing Hands Recovery actions range from gentle adjustments to aggressive interventions, always prioritizing system stability over perfect recovery. Graceful Degradation: Instead of complete failure, systems reduce functionality. YouTube serves lower-quality videos when CDN nodes fail rather than showing error pages. Progressive Recovery: Healing happens incrementally. One instance restarts at a time, with health verification before proceeding to the next. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://systemdr.substack.com/p/self-healing-systems-architectural) [comments] (https://www.reddit.com/r/programming/comments/1n39yxo/selfhealing_systems_architectural_patterns/)
The $69 Billion Domino Effect: How VMware’s Debt-Fueled Acquisition Is Killing Open Source, One Repository at a Time
https://www.reddit.com/r/programming/comments/1n3guzd/the_69_billion_domino_effect_how_vmwares/

<!-- SC_OFF -->Bitnami’s decision to end its free tier by August 2025 has sparked widespread outrage among developers who rely on its services. This change is part of Broadcom CEO Hock Tan’s strategy to monetize essential software following acquisitions, impacting countless users and forcing companies to either pay steep fees or undergo costly migrations. <!-- SC_ON --> submitted by /u/gamunu (https://www.reddit.com/user/gamunu)
[link] (https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time) [comments] (https://www.reddit.com/r/programming/comments/1n3guzd/the_69_billion_domino_effect_how_vmwares/)
Cognitive Load is what matters
https://www.reddit.com/r/programming/comments/1n3i1y1/cognitive_load_is_what_matters/

<!-- SC_OFF -->Hi! It was posted a few times in past year, but every time I get valuable feedback. Thanks! <!-- SC_ON --> submitted by /u/RobinCrusoe25 (https://www.reddit.com/user/RobinCrusoe25)
[link] (https://github.com/zakirullin/cognitive-load) [comments] (https://www.reddit.com/r/programming/comments/1n3i1y1/cognitive_load_is_what_matters/)
Internet Experiment Note Index
https://www.reddit.com/r/programming/comments/1n3scml/internet_experiment_note_index/

<!-- SC_OFF -->I'm a big fan of looking at the history of how foundational technologies evolved over time. This seems to be a collection of documents detailing the evolution and criticisms of early iterations of TCP and UDP. Hope other people also find this interesting! <!-- SC_ON --> submitted by /u/SereneCalathea (https://www.reddit.com/user/SereneCalathea)
[link] (https://www.rfc-editor.org/ien/ien-index.html) [comments] (https://www.reddit.com/r/programming/comments/1n3scml/internet_experiment_note_index/)
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/)