Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Revisiting YAGNI from an architectural perspective
https://www.reddit.com/r/programming/comments/1q89wd4/revisiting_yagni_from_an_architectural_perspective/

<!-- SC_OFF -->I learned YAGNI early and used it proudly. It saved me from over engineering, and if I am honest, it also gave me a very convenient way to avoid a few uncomfortable design conversations. After a few systems, rewrites, and more than one “we’ll fix it later” moment, my relationship with YAGNI changed. This is a short, reflective take on where YAGNI genuinely helps, where it quietly hurts, and why thinking ahead is not the same as building ahead. <!-- SC_ON --> submitted by /u/raysourav (https://www.reddit.com/user/raysourav)
[link] (https://medium.com/@souravray/yagni-you-arent-gonna-nail-it-until-you-do-a47d5fa303dd) [comments] (https://www.reddit.com/r/programming/comments/1q89wd4/revisiting_yagni_from_an_architectural_perspective/)
LSM-tree storage engines don't need to be complex to be exceptional - YouTube
https://www.reddit.com/r/programming/comments/1q8dqgv/lsmtree_storage_engines_dont_need_to_be_complex/

<!-- SC_OFF -->A pre-recording of the presentation I gave in the Database Internals Discord community about TidesDB. I hope you check it out :) <!-- SC_ON --> submitted by /u/diagraphic (https://www.reddit.com/user/diagraphic)
[link] (https://www.youtube.com/watch?v=7HROlAaiGVQ) [comments] (https://www.reddit.com/r/programming/comments/1q8dqgv/lsmtree_storage_engines_dont_need_to_be_complex/)
How do you build a mental model of a large unfamiliar codebase? I tried something different.
https://www.reddit.com/r/programming/comments/1q8j3so/how_do_you_build_a_mental_model_of_a_large/

<!-- SC_OFF -->For most programmers, building a mental model of unfamiliar source code, especially large codebases, is still a slow and often painful process. After years of working with large systems and reading open-source codebases (usually without anyone asking for help), I kept coming back to the same question: Is there a way to make junior developers ramp up like seniors? That question resurfaced today when I revisited some of my older projects to see how modern LLMs would approach them especially from UI/UX point of view as this always has been a place to improve for me as full-stack developer. And honestly, it was both exciting and unsettling. The truth is clear: LLMs are incredibly powerful in hands of people who know what they are doing. So instead of resisting that reality, this experiment embraces it. The idea is to transform an entire codebase into an interactive network graph, designed to dramatically reduce the time it takes to understand unfamiliar code and build a reliable mental model. I'm sharing an early demo to gather feedback, find early adopters, and potentially grow this into an open-source project. You will find Discord community I created for this in the YT video denoscription. <!-- SC_ON --> submitted by /u/DocsReader (https://www.reddit.com/user/DocsReader)
[link] (https://www.youtube.com/watch?v=sNAHa7SoFp4) [comments] (https://www.reddit.com/r/programming/comments/1q8j3so/how_do_you_build_a_mental_model_of_a_large/)
Replit boss: CEOs can vibe code their own prototypes and don't have to beg engineers for help anymore
https://www.reddit.com/r/programming/comments/1q8vm5v/replit_boss_ceos_can_vibe_code_their_own/

<!-- SC_OFF -->This is a bit of a vent: I've said it before and I will die on this hill: vibe coding is absolute brain rot, and the fact that it's being implicated in the suggestion that CEOs can pay themselves more and hire fewer people is outrageous. I bet his code looks like absolute horseshit 🤣 Masad said many leaders feel "disempowered because they've delegated a lot of things." Basically translates to: "I'm can't be arsed to learn how to program :( " A rough prototype, Masad said, allows leaders to ask a pointed question: Why should this take weeks to build if a version can be done in a few days? And this is actually just insane. He clearly knows jack all about the general process of software development. Anyway, I always hated Repilit anyway <!-- SC_ON --> submitted by /u/chronically-iconic (https://www.reddit.com/user/chronically-iconic)
[link] (https://share.google/CPwNzKaB0G5UADxXN) [comments] (https://www.reddit.com/r/programming/comments/1q8vm5v/replit_boss_ceos_can_vibe_code_their_own/)
Understanding the Decorator Design Pattern in Go: A Practical Guide
https://www.reddit.com/r/programming/comments/1q951tn/understanding_the_decorator_design_pattern_in_go/

<!-- SC_OFF -->Hey folks 👋 I just published a deep-dive blog on the Decorator Design Pattern in Go — one of those patterns you probably already use without realizing it (middleware, io.Reader, logging wrappers, etc.). The post walks through the pattern from a very practical, Go-centric angle: What the Decorator pattern really is (intent, definition, and the problem it solves) A clean, idiomatic Go implementation with interfaces How stacking multiple decorators actually works at runtime Common variations and extensions (logging, caching, compression) Performance & concurrency considerations in real systems Pros, cons, and common mistakes to avoid in Go If you’ve ever wrapped an http.Handler, chained bufio + gzip, or built middleware pipelines — this pattern is already part of your toolbox. The blog just puts a solid mental model behind it. Read here: https://medium.com/design-bootcamp/understanding-the-decorator-design-pattern-in-go-a-practical-guide-493b4048f953 <!-- SC_ON --> submitted by /u/priyankchheda15 (https://www.reddit.com/user/priyankchheda15)
[link] (https://medium.com/design-bootcamp/understanding-the-decorator-design-pattern-in-go-a-practical-guide-493b4048f953) [comments] (https://www.reddit.com/r/programming/comments/1q951tn/understanding_the_decorator_design_pattern_in_go/)