Reddit Programming – Telegram
Reddit Programming
212 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Build a Digital Bank (Step-by-Step Playlist)
https://www.reddit.com/r/programming/comments/1ov9epi/build_a_digital_bank_stepbystep_playlist/

<!-- SC_OFF -->This series walks through how to build a digital bank from scratch Tech Stack Spring Boot microservices (Customer, Account, Transaction, Payments, AuthUser, Consent) Auth0 for OAuth2 / JWT-based security PostgreSQL for persistence Key Concepts Covered Domain-Driven Design for financial services FDX-compliant API contracts (OpenAPI-first) Idempotency, ETags, and optimistic concurrency https://www.youtube.com/watch?v=VHBlkZYzSNY&list=PL4tLXdEa5XIWrhuhgJA1pdh2PDMrV7nMM&pp=gAQB0gcJCbAEOCosWNin <!-- SC_ON --> submitted by /u/AdPresent3286 (https://www.reddit.com/user/AdPresent3286)
[link] (https://www.youtube.com/watch?v=VHBlkZYzSNY&list=PL4tLXdEa5XIWrhuhgJA1pdh2PDMrV7nMM) [comments] (https://www.reddit.com/r/programming/comments/1ov9epi/build_a_digital_bank_stepbystep_playlist/)
Sacred Fig Architecture (FIG): an adaptive, feedback-driven alternative to Hexagonal — thoughts?
https://www.reddit.com/r/programming/comments/1ovdngg/sacred_fig_architecture_fig_an_adaptive/

<!-- SC_OFF -->Hey everyone, I’ve been working on Sacred Fig Architecture (FIG) — an evolution of Hexagonal that treats a system like a living tree: Trunk = pure domain core Roots = infrastructure adapters Branches = UI/API surfaces Canopy = composition & feature gating Aerial Roots = built-in telemetry/feedback that adapts policies at runtime Key idea: keep the domain pure and testable, but make feedback a first-class layer so the system can adjust (e.g., throttle workers, change caching strategy) without piercing domain boundaries. The repo has a whitepaper, diagrams, and a minimal example to try the layering and contracts. Repo: github.com/sanjuoo7live/sacred-fig-architecture (http://github.com/sanjuoo7live/sacred-fig-architecture) What I’d love feedback on: Does the Aerial Roots layer (feedback → canopy policy) feel like a clean way to add adaptation without contaminating the domain? Are the channel contracts (typed boundaries) enough to keep Branches/Roots from drifting into Trunk concerns? Would you adopt this as an architectural model/pattern alongside Hexagonal/Clean, or is it overkill unless you need runtime policy adaptation? Anything obvious missing in the minimal example or the guardrail docs (invariants/promotion policy)? Curious where this breaks, and where it shines. Tear it apart! 🌳 <!-- SC_ON --> submitted by /u/Resident-Escape-7959 (https://www.reddit.com/user/Resident-Escape-7959)
[link] (http://github.com/sanjuoo7live/sacred-fig-architecture) [comments] (https://www.reddit.com/r/programming/comments/1ovdngg/sacred_fig_architecture_fig_an_adaptive/)
Day 15: Gradients and Gradient Descent
https://www.reddit.com/r/programming/comments/1ovjarm/day_15_gradients_and_gradient_descent/

<!-- SC_OFF -->What We’ll Build Today Implement a basic gradient descent algorithm from scratch Train a simple AI model to predict house prices using gradient descent Visualize how AI systems “learn” by following gradients downhill Why This Matters: The Secret Behind Every AI System <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://aieworks.substack.com/p/day-15-gradients-and-gradient-descent) [comments] (https://www.reddit.com/r/programming/comments/1ovjarm/day_15_gradients_and_gradient_descent/)
LZAV 5.0: Improved compression ratio across a wide range of data types, at similar performance. Improved compression ratio by up to 5% for data smaller than 256 KiB. Fast Data Compression Algorithm (header-only C/C++).
https://www.reddit.com/r/programming/comments/1ovyqle/lzav_50_improved_compression_ratio_across_a_wide/

submitted by /u/avaneev (https://www.reddit.com/user/avaneev)
[link] (https://github.com/avaneev/lzav) [comments] (https://www.reddit.com/r/programming/comments/1ovyqle/lzav_50_improved_compression_ratio_across_a_wide/)
Raft Consensus in 2,000 words
https://www.reddit.com/r/programming/comments/1ow0czt/raft_consensus_in_2000_words/

<!-- SC_OFF -->Very accessible article about the Raft Consensus Algorithm - which solves the problem of choosing the leader in a distributed system environment. It's used in many popular tools and libraries, such as Etcd (database behind Kubernetes state), MongoDB or Apache Kafka. So it's definitely worth wrapping one's head around it; and as for a complex problem of this nature it's surprisingly straightforward and the linked article does a great job at explaining it in detail. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://news.alvaroduran.com/p/raft-consensus-in-2000-words) [comments] (https://www.reddit.com/r/programming/comments/1ow0czt/raft_consensus_in_2000_words/)