Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
(s)coping with code comments
https://www.reddit.com/r/programming/comments/1pbc59i/scoping_with_code_comments/

<!-- SC_OFF -->The problem of scope ambiguity of code comments and what to do about it. <!-- SC_ON --> submitted by /u/Beofli (https://www.reddit.com/user/Beofli)
[link] (https://mcvisser.eu/2025/12/01/scoping-with-code-comments/) [comments] (https://www.reddit.com/r/programming/comments/1pbc59i/scoping_with_code_comments/)
19-Year-Old Dev Diving Into ECS, SFINAE & CRTP
https://www.reddit.com/r/programming/comments/1pbw6d8/19yearold_dev_diving_into_ecs_sfinae_crtp/

<!-- SC_OFF -->Hi! Just before you read, I just want to say that I'm not very familiar with Reddit and its posting culture, so I'm not sure if it's okay to post something like this, but I'll try anyway :) I'm 19 years old and I've been programming for a little over two years. I'm a computer science student, but I also dedicate a lot of my free time to experimenting and learning. I write code as an art lol: I appreciate every moment and I love pushing myself to learn advanced concepts. Lately, I've been immersed in game engine design, particularly around ECS and related systems. My GitHub contains experiments and projects where I explore topics such as: SFINAE and template metaprogramming Variadic programming and movement semantics Static polymorphism (CRTP/SRTP) ECS frameworks and engine architecture I'd love to get feedback, comments, or simply chat about code and design with someone. I know it's a lot to ask, but if you're curious, my github is linked to the post. Thanks for visiting! <!-- SC_ON --> submitted by /u/Mysticatly (https://www.reddit.com/user/Mysticatly)
[link] (https://github.com/unrays) [comments] (https://www.reddit.com/r/programming/comments/1pbw6d8/19yearold_dev_diving_into_ecs_sfinae_crtp/)
Is this code clean? A critical look at Clean Code 2nd Edition
https://www.reddit.com/r/programming/comments/1pc5xyy/is_this_code_clean_a_critical_look_at_clean_code/

<!-- SC_OFF -->I read Clean Code 2nd edition wondering if Martin had evolved past the old critiques.
After Part 1, he mostly hasn’t — the core style and assumptions are basically unchanged. <!-- SC_ON --> submitted by /u/Soggy_Sprinkles3619 (https://www.reddit.com/user/Soggy_Sprinkles3619)
[link] (https://bugzmanov.github.io/cleancode-critique/clean_code_second_edition_review.html) [comments] (https://www.reddit.com/r/programming/comments/1pc5xyy/is_this_code_clean_a_critical_look_at_clean_code/)
Advanced, Overlooked Python Typing
https://www.reddit.com/r/programming/comments/1pc9uql/advanced_overlooked_python_typing/

<!-- SC_OFF -->While quantitative research in software engineering is difficult to trust most of the time, some studies claim that type checking can reduce bugs by about 15% in Python. This post covers advanced typing features such as never types, type guards, concatenate, etc., that are often overlooked but can make a codebase more maintainable and easier to work with <!-- SC_ON --> submitted by /u/Martynoas (https://www.reddit.com/user/Martynoas)
[link] (https://martynassubonis.substack.com/p/advanced-overlooked-python-typing) [comments] (https://www.reddit.com/r/programming/comments/1pc9uql/advanced_overlooked_python_typing/)
Choosing your starting line in enterprise architecture
https://www.reddit.com/r/programming/comments/1pcdc6b/choosing_your_starting_line_in_enterprise/

<!-- SC_OFF -->If you start up an enterprise architecture office, you have two types of strategies people use. Some people start by mapping everything that exists, in whatever state it happens to be. They then assess what they have and start building a gap analysis towards a better, more uniform state. The other group of people start at the end point and work their way back. They sketch out the ideal state and map out the bare essentials towards getting there. The big upside of the AS-IS approach is that you are working with terms and information that is familiar to the organization. People will recognize the works you are linking applications and business units to, as they probably use them themselves. The idea of skipping the AS-IS altogether comes down to: why base our architecture on structures that are not only, very low quality, they are also probably not carried in the organization. The architecture maturity of the organization is probably very low, so why take on the burden. My experiences has taught me mainly: If something already exists and people use it, adopt it. If everything is a mess and nobody agrees on anything, skip the archaeology and design something that makes sense to you. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2025-11-28-choosing-your-starting-line-in-enterprise-architecture/) [comments] (https://www.reddit.com/r/programming/comments/1pcdc6b/choosing_your_starting_line_in_enterprise/)