Rethinking Helix
https://www.reddit.com/r/programming/comments/1qa9m6o/rethinking_helix/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://asta.boserup.eu/forest/rethinking-helix/) [comments] (https://www.reddit.com/r/programming/comments/1qa9m6o/rethinking_helix/)
https://www.reddit.com/r/programming/comments/1qa9m6o/rethinking_helix/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://asta.boserup.eu/forest/rethinking-helix/) [comments] (https://www.reddit.com/r/programming/comments/1qa9m6o/rethinking_helix/)
LLVM: The bad parts
https://www.reddit.com/r/programming/comments/1qaeile/llvm_the_bad_parts/
submitted by /u/Necrotos (https://www.reddit.com/user/Necrotos)
[link] (https://www.npopov.com/2026/01/11/LLVM-The-bad-parts.html) [comments] (https://www.reddit.com/r/programming/comments/1qaeile/llvm_the_bad_parts/)
https://www.reddit.com/r/programming/comments/1qaeile/llvm_the_bad_parts/
submitted by /u/Necrotos (https://www.reddit.com/user/Necrotos)
[link] (https://www.npopov.com/2026/01/11/LLVM-The-bad-parts.html) [comments] (https://www.reddit.com/r/programming/comments/1qaeile/llvm_the_bad_parts/)
The C++ Compiler Is A Nightmare!
https://www.reddit.com/r/programming/comments/1qagtj3/the_c_compiler_is_a_nightmare/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=NQesrVuraUc) [comments] (https://www.reddit.com/r/programming/comments/1qagtj3/the_c_compiler_is_a_nightmare/)
https://www.reddit.com/r/programming/comments/1qagtj3/the_c_compiler_is_a_nightmare/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=NQesrVuraUc) [comments] (https://www.reddit.com/r/programming/comments/1qagtj3/the_c_compiler_is_a_nightmare/)
Maybe the database got it right
https://www.reddit.com/r/programming/comments/1qaguow/maybe_the_database_got_it_right/
submitted by /u/fernandohur (https://www.reddit.com/user/fernandohur)
[link] (https://fhur.me/posts/2026/maybe-the-database-got-it-right) [comments] (https://www.reddit.com/r/programming/comments/1qaguow/maybe_the_database_got_it_right/)
https://www.reddit.com/r/programming/comments/1qaguow/maybe_the_database_got_it_right/
submitted by /u/fernandohur (https://www.reddit.com/user/fernandohur)
[link] (https://fhur.me/posts/2026/maybe-the-database-got-it-right) [comments] (https://www.reddit.com/r/programming/comments/1qaguow/maybe_the_database_got_it_right/)
C++26 - What's In It For You? - Marc Gregoire - CppCon 2025
https://www.reddit.com/r/programming/comments/1qah2k3/c26_whats_in_it_for_you_marc_gregoire_cppcon_2025/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=PcidhLUYp-4) [comments] (https://www.reddit.com/r/programming/comments/1qah2k3/c26_whats_in_it_for_you_marc_gregoire_cppcon_2025/)
https://www.reddit.com/r/programming/comments/1qah2k3/c26_whats_in_it_for_you_marc_gregoire_cppcon_2025/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=PcidhLUYp-4) [comments] (https://www.reddit.com/r/programming/comments/1qah2k3/c26_whats_in_it_for_you_marc_gregoire_cppcon_2025/)
YAML? That’s Norway problem
https://www.reddit.com/r/programming/comments/1qaroyn/yaml_thats_norway_problem/
submitted by /u/merelysounds (https://www.reddit.com/user/merelysounds)
[link] (https://lab174.com/blog/202601-yaml-norway/) [comments] (https://www.reddit.com/r/programming/comments/1qaroyn/yaml_thats_norway_problem/)
https://www.reddit.com/r/programming/comments/1qaroyn/yaml_thats_norway_problem/
submitted by /u/merelysounds (https://www.reddit.com/user/merelysounds)
[link] (https://lab174.com/blog/202601-yaml-norway/) [comments] (https://www.reddit.com/r/programming/comments/1qaroyn/yaml_thats_norway_problem/)
Domain-Composed Models (DCM): a pragmatic middle ground between Active Record and Clean DDD
https://www.reddit.com/r/programming/comments/1qast8w/domaincomposed_models_dcm_a_pragmatic_middle/
<!-- SC_OFF -->I wrote an article exploring a pattern we converged on in practice when Active Record became too coupled, but repository-heavy Clean DDD felt like unnecessary ceremony for the problem at hand. The idea is to keep domain behavior close to ORM-backed models, while expressing business rules in infra-agnostic mixins that depend on explicit behavioral contracts (hooks). The concrete model implements those hooks using persistence concerns. It’s not a replacement for DDD, and not a defense of Active Record either — more an attempt to formalize a pragmatic middle ground that many teams seem to arrive at organically. The article uses a simple hotel booking example (Python / SQLAlchemy), discusses trade-offs limits of the pattern, and explains where other approaches fit better. Article: https://medium.com/@hamza-senhajirhazi/domain-composed-models-dcm-a-pragmatic-middle-ground-between-active-record-and-clean-ddd-e44172a58246 I’d be genuinely interested in counter-examples or critiques—especially from people who’ve applied DDD in production systems. <!-- SC_ON --> submitted by /u/senhaj_h (https://www.reddit.com/user/senhaj_h)
[link] (https://medium.com/@hamza-senhajirhazi/domain-composed-models-dcm-a-pragmatic-middle-ground-between-active-record-and-clean-ddd-e44172a58246) [comments] (https://www.reddit.com/r/programming/comments/1qast8w/domaincomposed_models_dcm_a_pragmatic_middle/)
https://www.reddit.com/r/programming/comments/1qast8w/domaincomposed_models_dcm_a_pragmatic_middle/
<!-- SC_OFF -->I wrote an article exploring a pattern we converged on in practice when Active Record became too coupled, but repository-heavy Clean DDD felt like unnecessary ceremony for the problem at hand. The idea is to keep domain behavior close to ORM-backed models, while expressing business rules in infra-agnostic mixins that depend on explicit behavioral contracts (hooks). The concrete model implements those hooks using persistence concerns. It’s not a replacement for DDD, and not a defense of Active Record either — more an attempt to formalize a pragmatic middle ground that many teams seem to arrive at organically. The article uses a simple hotel booking example (Python / SQLAlchemy), discusses trade-offs limits of the pattern, and explains where other approaches fit better. Article: https://medium.com/@hamza-senhajirhazi/domain-composed-models-dcm-a-pragmatic-middle-ground-between-active-record-and-clean-ddd-e44172a58246 I’d be genuinely interested in counter-examples or critiques—especially from people who’ve applied DDD in production systems. <!-- SC_ON --> submitted by /u/senhaj_h (https://www.reddit.com/user/senhaj_h)
[link] (https://medium.com/@hamza-senhajirhazi/domain-composed-models-dcm-a-pragmatic-middle-ground-between-active-record-and-clean-ddd-e44172a58246) [comments] (https://www.reddit.com/r/programming/comments/1qast8w/domaincomposed_models_dcm_a_pragmatic_middle/)
Vibe Coding Debt: The Security Risks of AI-Generated Codebases
https://www.reddit.com/r/programming/comments/1qauuls/vibe_coding_debt_the_security_risks_of/
submitted by /u/JadeLuxe (https://www.reddit.com/user/JadeLuxe)
[link] (https://instatunnel.my/blog/vibe-coding-debt-the-security-risks-of-ai-generated-codebases) [comments] (https://www.reddit.com/r/programming/comments/1qauuls/vibe_coding_debt_the_security_risks_of/)
https://www.reddit.com/r/programming/comments/1qauuls/vibe_coding_debt_the_security_risks_of/
submitted by /u/JadeLuxe (https://www.reddit.com/user/JadeLuxe)
[link] (https://instatunnel.my/blog/vibe-coding-debt-the-security-risks-of-ai-generated-codebases) [comments] (https://www.reddit.com/r/programming/comments/1qauuls/vibe_coding_debt_the_security_risks_of/)
BTS of OpenTelemetry Auto-instrumentation
https://www.reddit.com/r/programming/comments/1qavzd8/bts_of_opentelemetry_autoinstrumentation/
submitted by /u/elizObserves (https://www.reddit.com/user/elizObserves)
[link] (https://newsletter.signoz.io/p/bts-of-opentelemetry-auto-instrumentation) [comments] (https://www.reddit.com/r/programming/comments/1qavzd8/bts_of_opentelemetry_autoinstrumentation/)
https://www.reddit.com/r/programming/comments/1qavzd8/bts_of_opentelemetry_autoinstrumentation/
submitted by /u/elizObserves (https://www.reddit.com/user/elizObserves)
[link] (https://newsletter.signoz.io/p/bts-of-opentelemetry-auto-instrumentation) [comments] (https://www.reddit.com/r/programming/comments/1qavzd8/bts_of_opentelemetry_autoinstrumentation/)
Bring back opinionated architecture
https://www.reddit.com/r/programming/comments/1qayazp/bring_back_opinionated_architecture/
<!-- SC_OFF -->Enterprise architecture claims to bring clarity, but often hides behind ambiguity. And maybe that’s something we need to confront. When I was a developer, I was always attracted to highly opinionated libraries and frameworks. I always preferred a single way of doing things, over three different ways to do it, and they all have their pros and cons. This is something Enterprise Architecture really struggles with I feel. We tend to overengineer things. We would rather build a tool with 3 different data interfaces, than commit to 1 well thought out interface. Don’t get me wrong, I’m not advocating here for abandoning backup plans and putting all your eggs in one basket. What I am advocating for is architectural courage. Are all these “it depends” and “future-proofing” mantras there to get to a more correct solution, or just there to minimize your personal responsibility if it all goes haywire? You also have to calculate the cost of it all. In the above scenario where you cover all your bases and build a REST API and an sFTP connection because “you might need it in the future”, you will have to maintain, secure, document, train and test both. For years to come. Just another think that can break. That would be ok if that scenario actually plays out. If the company strategy changes, and the company never connects the two applications, all of that has been for nothing. Then there is the conversation of the easy-off ramp in implementing new software. It’s cool that you can hot swap your incoming data from one service to a different one in less than a week! Now we just need six months of new training, new processes, new KPIs, new goal setting and hiring to use said new data source. I’m not suggesting we should all become architectural “dictators” who refuse to listen to edge cases. But I am suggesting that we stop being so deep into “what-if” and start focusing more on “what-is.” Being opinionated doesn’t mean being rigid, it’s more about actually having a plan. It means having the courage to say, “This is the path we are taking because it is the most efficient one for today.” If the strategy changes in two years, you deal with it then, with the benefit of two years of lower maintenance costs and a leaner system. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2026-01-09-bring-back-opinionated-architecture/) [comments] (https://www.reddit.com/r/programming/comments/1qayazp/bring_back_opinionated_architecture/)
https://www.reddit.com/r/programming/comments/1qayazp/bring_back_opinionated_architecture/
<!-- SC_OFF -->Enterprise architecture claims to bring clarity, but often hides behind ambiguity. And maybe that’s something we need to confront. When I was a developer, I was always attracted to highly opinionated libraries and frameworks. I always preferred a single way of doing things, over three different ways to do it, and they all have their pros and cons. This is something Enterprise Architecture really struggles with I feel. We tend to overengineer things. We would rather build a tool with 3 different data interfaces, than commit to 1 well thought out interface. Don’t get me wrong, I’m not advocating here for abandoning backup plans and putting all your eggs in one basket. What I am advocating for is architectural courage. Are all these “it depends” and “future-proofing” mantras there to get to a more correct solution, or just there to minimize your personal responsibility if it all goes haywire? You also have to calculate the cost of it all. In the above scenario where you cover all your bases and build a REST API and an sFTP connection because “you might need it in the future”, you will have to maintain, secure, document, train and test both. For years to come. Just another think that can break. That would be ok if that scenario actually plays out. If the company strategy changes, and the company never connects the two applications, all of that has been for nothing. Then there is the conversation of the easy-off ramp in implementing new software. It’s cool that you can hot swap your incoming data from one service to a different one in less than a week! Now we just need six months of new training, new processes, new KPIs, new goal setting and hiring to use said new data source. I’m not suggesting we should all become architectural “dictators” who refuse to listen to edge cases. But I am suggesting that we stop being so deep into “what-if” and start focusing more on “what-is.” Being opinionated doesn’t mean being rigid, it’s more about actually having a plan. It means having the courage to say, “This is the path we are taking because it is the most efficient one for today.” If the strategy changes in two years, you deal with it then, with the benefit of two years of lower maintenance costs and a leaner system. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2026-01-09-bring-back-opinionated-architecture/) [comments] (https://www.reddit.com/r/programming/comments/1qayazp/bring_back_opinionated_architecture/)
Complexity, logic and data
https://www.reddit.com/r/programming/comments/1qayyfb/complexity_logic_and_data/
submitted by /u/alcoholov (https://www.reddit.com/user/alcoholov)
[link] (https://legacyfreecode.medium.com/solving-essential-complexity-8f932de3a467) [comments] (https://www.reddit.com/r/programming/comments/1qayyfb/complexity_logic_and_data/)
https://www.reddit.com/r/programming/comments/1qayyfb/complexity_logic_and_data/
submitted by /u/alcoholov (https://www.reddit.com/user/alcoholov)
[link] (https://legacyfreecode.medium.com/solving-essential-complexity-8f932de3a467) [comments] (https://www.reddit.com/r/programming/comments/1qayyfb/complexity_logic_and_data/)
Your First Quantum Circuit in Python (Qiskit 2026 Guide)
https://www.reddit.com/r/programming/comments/1qb005o/your_first_quantum_circuit_in_python_qiskit_2026/
submitted by /u/thecoode (https://www.reddit.com/user/thecoode)
[link] (https://python.plainenglish.io/your-first-quantum-circuit-in-python-qiskit-2026-guide-df40d2e98c0d) [comments] (https://www.reddit.com/r/programming/comments/1qb005o/your_first_quantum_circuit_in_python_qiskit_2026/)
https://www.reddit.com/r/programming/comments/1qb005o/your_first_quantum_circuit_in_python_qiskit_2026/
submitted by /u/thecoode (https://www.reddit.com/user/thecoode)
[link] (https://python.plainenglish.io/your-first-quantum-circuit-in-python-qiskit-2026-guide-df40d2e98c0d) [comments] (https://www.reddit.com/r/programming/comments/1qb005o/your_first_quantum_circuit_in_python_qiskit_2026/)
Tech Debt: The Hidden Cost of “Quick Fixes”
https://www.reddit.com/r/programming/comments/1qb3mfc/tech_debt_the_hidden_cost_of_quick_fixes/
submitted by /u/sparkestine (https://www.reddit.com/user/sparkestine)
[link] (https://blog.mrinalmaheshwari.com/tech-debt-explained-simple-words-9ce90e70eb37) [comments] (https://www.reddit.com/r/programming/comments/1qb3mfc/tech_debt_the_hidden_cost_of_quick_fixes/)
https://www.reddit.com/r/programming/comments/1qb3mfc/tech_debt_the_hidden_cost_of_quick_fixes/
submitted by /u/sparkestine (https://www.reddit.com/user/sparkestine)
[link] (https://blog.mrinalmaheshwari.com/tech-debt-explained-simple-words-9ce90e70eb37) [comments] (https://www.reddit.com/r/programming/comments/1qb3mfc/tech_debt_the_hidden_cost_of_quick_fixes/)
Quotes from "A Pattern Language" (Origin of Design Patterns)
https://www.reddit.com/r/programming/comments/1qb6czi/quotes_from_a_pattern_language_origin_of_design/
<!-- SC_OFF -->"Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice." "The patterns are still hypotheses, all 253 of them - and are therefore all tentative, all free to evolve under the impact of new experience and observation." "Every society which is alive and whole, will have its own unique and distinct pattern language ... every individual in such a society will have a unique language, shared in part, but which as a totality is unique to the mind of the person who has it." "In what frame of mind, and with what intention, are we publishing this language here? The fact that it is published as a book means that many thousands of people can use it. Is it not true that there is a danger that people might come to rely on this one printed language, instead of developing their own languages, in their own minds?" "The fact is, that we have written this book as a first step in the society-wide process by which people will gradually become conscious of their own pattern languages, and work to improve them." "When in doubt about a pattern, don't include it." "There are often cases where you may have a personal version version of a pattern, which is more true, or more relevant for you." <!-- SC_ON --> submitted by /u/SpeedyPuzzlement (https://www.reddit.com/user/SpeedyPuzzlement)
[link] (https://arl.human.cornell.edu/linked%20docs/Alexander_A_Pattern_Language.pdf) [comments] (https://www.reddit.com/r/programming/comments/1qb6czi/quotes_from_a_pattern_language_origin_of_design/)
https://www.reddit.com/r/programming/comments/1qb6czi/quotes_from_a_pattern_language_origin_of_design/
<!-- SC_OFF -->"Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice." "The patterns are still hypotheses, all 253 of them - and are therefore all tentative, all free to evolve under the impact of new experience and observation." "Every society which is alive and whole, will have its own unique and distinct pattern language ... every individual in such a society will have a unique language, shared in part, but which as a totality is unique to the mind of the person who has it." "In what frame of mind, and with what intention, are we publishing this language here? The fact that it is published as a book means that many thousands of people can use it. Is it not true that there is a danger that people might come to rely on this one printed language, instead of developing their own languages, in their own minds?" "The fact is, that we have written this book as a first step in the society-wide process by which people will gradually become conscious of their own pattern languages, and work to improve them." "When in doubt about a pattern, don't include it." "There are often cases where you may have a personal version version of a pattern, which is more true, or more relevant for you." <!-- SC_ON --> submitted by /u/SpeedyPuzzlement (https://www.reddit.com/user/SpeedyPuzzlement)
[link] (https://arl.human.cornell.edu/linked%20docs/Alexander_A_Pattern_Language.pdf) [comments] (https://www.reddit.com/r/programming/comments/1qb6czi/quotes_from_a_pattern_language_origin_of_design/)
A Developer’s Guide to Naming Things Right
https://www.reddit.com/r/programming/comments/1qb6v0n/a_developers_guide_to_naming_things_right/
submitted by /u/sparkestine (https://www.reddit.com/user/sparkestine)
[link] (https://blog.stackademic.com/developer-guide-naming-conventions-a66203fd5665) [comments] (https://www.reddit.com/r/programming/comments/1qb6v0n/a_developers_guide_to_naming_things_right/)
https://www.reddit.com/r/programming/comments/1qb6v0n/a_developers_guide_to_naming_things_right/
submitted by /u/sparkestine (https://www.reddit.com/user/sparkestine)
[link] (https://blog.stackademic.com/developer-guide-naming-conventions-a66203fd5665) [comments] (https://www.reddit.com/r/programming/comments/1qb6v0n/a_developers_guide_to_naming_things_right/)
While everyone Is Talking About AI, GAC Is Coming for Your Job
https://www.reddit.com/r/programming/comments/1qb71ay/while_everyone_is_talking_about_ai_gac_is_coming/
<!-- SC_OFF -->There has been a lot of industry is dead and other doomsayer type opinions in regards to. This post represents my 2c. <!-- SC_ON --> submitted by /u/myFullNameWasTaken (https://www.reddit.com/user/myFullNameWasTaken)
[link] (https://blog.cvetic.in.rs/philosophy/while-everyone-is-talking-about-ai-gac-is-coming-for-your-job/) [comments] (https://www.reddit.com/r/programming/comments/1qb71ay/while_everyone_is_talking_about_ai_gac_is_coming/)
https://www.reddit.com/r/programming/comments/1qb71ay/while_everyone_is_talking_about_ai_gac_is_coming/
<!-- SC_OFF -->There has been a lot of industry is dead and other doomsayer type opinions in regards to. This post represents my 2c. <!-- SC_ON --> submitted by /u/myFullNameWasTaken (https://www.reddit.com/user/myFullNameWasTaken)
[link] (https://blog.cvetic.in.rs/philosophy/while-everyone-is-talking-about-ai-gac-is-coming-for-your-job/) [comments] (https://www.reddit.com/r/programming/comments/1qb71ay/while_everyone_is_talking_about_ai_gac_is_coming/)
Mastering Memory Management and Garbage Collection in .NET
https://www.reddit.com/r/programming/comments/1qb909x/mastering_memory_management_and_garbage/
submitted by /u/ReverseBlade (https://www.reddit.com/user/ReverseBlade)
[link] (https://nemorize.com/roadmaps/mastering-memory-management-and-garbage-collection-in-net) [comments] (https://www.reddit.com/r/programming/comments/1qb909x/mastering_memory_management_and_garbage/)
https://www.reddit.com/r/programming/comments/1qb909x/mastering_memory_management_and_garbage/
submitted by /u/ReverseBlade (https://www.reddit.com/user/ReverseBlade)
[link] (https://nemorize.com/roadmaps/mastering-memory-management-and-garbage-collection-in-net) [comments] (https://www.reddit.com/r/programming/comments/1qb909x/mastering_memory_management_and_garbage/)