Reddit Programming
201 subscribers
1.22K photos
126K links
I will send you newest post from subreddit /r/programming
Download Telegram
I am working on something to make following tutorials alot easier.
https://www.reddit.com/r/programming/comments/1s4tupd/i_am_working_on_something_to_make_following/

<!-- SC_OFF -->Does anybody else find themselves having a tab mess when doing tutorials. Especially with multiple sources and docs/readmes to follow for smth like remixing. <!-- SC_ON --> submitted by /u/BruhMomentBruhuno (https://www.reddit.com/user/BruhMomentBruhuno)
[link] (http://comingsoon.com/) [comments] (https://www.reddit.com/r/programming/comments/1s4tupd/i_am_working_on_something_to_make_following/)
TeamPCP strikes again - telnyx 4.87.1 and 4.87.2 on PyPI are malicious
https://www.reddit.com/r/programming/comments/1s50g5t/teampcp_strikes_again_telnyx_4871_and_4872_on/

<!-- SC_OFF -->Same actor, same RSA key, same tpcp.tar.gz exfiltration header as the litellm compromise last week. This time they injected into telnyx/_client.py - triggers on import telnyx, no user interaction needed. New trick: payload is hidden inside WAV audio files using steganography to bypass network inspection. On Linux/macOS: steals credentials, encrypts with AES-256 + RSA-4096, exfiltrates to their C2. On Windows: drops a persistent binary in the Startup folder named msbuild.exe. They even pushed a quick 4.87.2 bugfix to fix a casing error that was breaking the Windows path. These folks are paying attention.
Pin to telnyx==4.87.0. Rotate creds if you installed either version. Full analysis with IoCs here https://safedep.io/malicious-telnyx-pypi-compromise/ <!-- SC_ON --> submitted by /u/No_Plan_3442 (https://www.reddit.com/user/No_Plan_3442)
[link] (https://safedep.io/malicious-telnyx-pypi-compromise/) [comments] (https://www.reddit.com/r/programming/comments/1s50g5t/teampcp_strikes_again_telnyx_4871_and_4872_on/)
Don’t shave that yak! (How we added Go to Visual Studio)
https://www.reddit.com/r/programming/comments/1s523ig/dont_shave_that_yak_how_we_added_go_to_visual/

<!-- SC_OFF -->Hi all, author here. TL;DR: We wanted to work with Go code within our main project, but without leaving Visual Studio. So we started a "weekend-size" task of integrating Go into VS and discovered a few things along the way. <!-- SC_ON --> submitted by /u/axkotti (https://www.reddit.com/user/axkotti)
[link] (https://blog.axiorema.com/engineering/dont-shave-that-yak-go-in-visual-studio/) [comments] (https://www.reddit.com/r/programming/comments/1s523ig/dont_shave_that_yak_how_we_added_go_to_visual/)
How I rediscovered ( or discovered ) the right way to use Typescript Interface to do Dependency Inversion
https://www.reddit.com/r/programming/comments/1s5vb70/how_i_rediscovered_or_discovered_the_right_way_to/

<!-- SC_OFF -->Hexagonal architecture, contract-first / API-first / interface first are just multiple names for the same concept of the D in SOLID - Dependency Inversion. What Dependency Inversion means that instead of a top-down coupling ( like how your repository services might coupled to a Postgres database service App -> DB ), both are actually only tightly couple to the interface App -> Interface <- DB ( see the inversion here ? ). So instead of teams writing the implementation first, both should sit down and think about the API and Interface between services or between Backend / Frontend, thus allow people to work independently ( with the least back and forth ) during the implementation phase. <!-- SC_ON --> submitted by /u/No-Performance-785 (https://www.reddit.com/user/No-Performance-785)
[link] (https://substack.com/@thoughtzip/note/p-192388940) [comments] (https://www.reddit.com/r/programming/comments/1s5vb70/how_i_rediscovered_or_discovered_the_right_way_to/)
Backend from first principles
https://www.reddit.com/r/programming/comments/1s7gp8m/backend_from_first_principles/

<!-- SC_OFF -->Most backend discussions start with tools. But systems don’t fail because of tools—they fail when fundamentals are unclear. This is Part 2 of my blog series on understanding backend systems from the ground up. In this part, I focused on questions that come up as systems start to grow: Why does REST look the way it does? How do databases behave under increasing load? When does caching actually help—and when can it backfire? Why do background jobs become necessary in real systems? The idea is to move beyond “how to use X” and instead understand the reasoning behind common backend patterns. If you’re working on backend systems or preparing for system design, this might be useful. <!-- SC_ON --> submitted by /u/No-Demand1385 (https://www.reddit.com/user/No-Demand1385)
[link] (https://medium.com/@karthik.joshi103/backend-from-first-principles-91eaf3720e38) [comments] (https://www.reddit.com/r/programming/comments/1s7gp8m/backend_from_first_principles/)