My favourite small hash table
https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://www.corsix.org/content/my-favourite-small-hash-table) [comments] (https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/)
https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://www.corsix.org/content/my-favourite-small-hash-table) [comments] (https://www.reddit.com/r/programming/comments/1pigued/my_favourite_small_hash_table/)
Easy microservices in .NET with RabbitMQ
https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/
<!-- SC_OFF -->Tutorial for programming microservices using the RFRabbitMQRPC NuGet library in a simple way with a .NET Web API-based framework <!-- SC_ON --> submitted by /u/Last_Enthusiasm1810 (https://www.reddit.com/user/Last_Enthusiasm1810)
[link] (https://www.youtube.com/watch?v=hrU-upEMlPk) [comments] (https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/)
https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/
<!-- SC_OFF -->Tutorial for programming microservices using the RFRabbitMQRPC NuGet library in a simple way with a .NET Web API-based framework <!-- SC_ON --> submitted by /u/Last_Enthusiasm1810 (https://www.reddit.com/user/Last_Enthusiasm1810)
[link] (https://www.youtube.com/watch?v=hrU-upEMlPk) [comments] (https://www.reddit.com/r/programming/comments/1pijfsl/easy_microservices_in_net_with_rabbitmq/)
How I Cultivated an Open-source Platform for learning Japanese from scratch
https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/
<!-- SC_OFF -->When I first started building my own web app for grinding kanji and Japanese vocabulary, I wasn’t planning to build a serious learning platform or anything like that. I just wanted a simple, free way to practice and learn the Japanese kana (which is essentially the Japanese alphabet, though it's more accurately described as a syllabary) - something that felt as clean and addictive as Monkeytype, but for language learners. At the time, I was a student and a solo dev (and I still am). I didn’t have a marketing budget, a team or even a clear roadmap. But I did have one goal: Build the kind of learning tool I wish existed when I started learning Japanese. Fast forward a year later, and the platform now has 10k+ monthly users and almost 1k stars on GitHub. Here’s everything I learned after almost a year. 1. Build Something You Yourself Would Use First Initially, I built my app only for myself. I was frustrated with how complicated or paywalled most Japanese learning apps felt. I wanted something fast, minimalist and distraction-free. That mindset made the first version simple but focused. I didn’t chase every feature, but just focused on one thing done extremely well: Helping myself internalize the Japanese kana through repetition, feedback and flow, with the added aesthetics and customizability inspired by Monkeytype. That focus attracted other learners who wanted exactly the same thing. 2. Open Source Early, Even When It Feels “Not Ready” The first commits were honestly messy. Actually, I even exposed my project's Google Analytics API keys at one point lol. Still, putting my app on GitHub very early on changed everything. Even when the project had 0 stars on GitHub and no real contributors, open-sourcing my app still gave my productivity a much-needed boost, because I now felt "seen" and thus had to polish and update my project regularly in the case that someone would eventually see it (and decide to roast me and my code). That being said, the real breakthrough came after I started posting about my app on Reddit, Discord and other online forums. People started opening issues, suggesting improvements and even sending pull requests. Suddenly, it wasn’t my project anymore - it became our project. The community helped me shape the roadmap, catch bugs and add features I wouldn’t have thought of alone, and took my app in an amazing direction I never would've thought of myself. 3. Focus on Design and Experience, Not Just Code A lot of open-source tools look like developer experiments - especially the project my app was initially based off of, kana pro (yes, you can google "kana pro" - it's a real website, and it's very ugly). I wanted my app to feel like a polished product - something a beginner could open and instantly understand, and also appreciate the beauty of the app's minimalist, aesthetic design. That meant obsessing over: Smooth animations and feedback loops Clean typography and layout Accessibility and mobile-first design I treated UX like part of the core functionality, not an afterthought - and users notice. Of course, the design is still far from perfect, but most users praise our unique, streamlined, no-frills approach and simplicity in terms of UI. 4. Build in Public (and Be Genuine About It) I regularly shared progress on Reddit, Discord, and a few Japanese-learning communities - not as ads, but as updates from a passionate learner. Even though I got downvoted and hated on dozens of times, people still responded to my authenticity. I wasn’t selling anything. I was just sharing something I built out of love for the language and for coding. Eventually, that transparency built trust and word-of-mouth growth that no paid marketing campaign could buy. 5. Community > Marketing My app's community has been everything. They’ve built
https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/
<!-- SC_OFF -->When I first started building my own web app for grinding kanji and Japanese vocabulary, I wasn’t planning to build a serious learning platform or anything like that. I just wanted a simple, free way to practice and learn the Japanese kana (which is essentially the Japanese alphabet, though it's more accurately described as a syllabary) - something that felt as clean and addictive as Monkeytype, but for language learners. At the time, I was a student and a solo dev (and I still am). I didn’t have a marketing budget, a team or even a clear roadmap. But I did have one goal: Build the kind of learning tool I wish existed when I started learning Japanese. Fast forward a year later, and the platform now has 10k+ monthly users and almost 1k stars on GitHub. Here’s everything I learned after almost a year. 1. Build Something You Yourself Would Use First Initially, I built my app only for myself. I was frustrated with how complicated or paywalled most Japanese learning apps felt. I wanted something fast, minimalist and distraction-free. That mindset made the first version simple but focused. I didn’t chase every feature, but just focused on one thing done extremely well: Helping myself internalize the Japanese kana through repetition, feedback and flow, with the added aesthetics and customizability inspired by Monkeytype. That focus attracted other learners who wanted exactly the same thing. 2. Open Source Early, Even When It Feels “Not Ready” The first commits were honestly messy. Actually, I even exposed my project's Google Analytics API keys at one point lol. Still, putting my app on GitHub very early on changed everything. Even when the project had 0 stars on GitHub and no real contributors, open-sourcing my app still gave my productivity a much-needed boost, because I now felt "seen" and thus had to polish and update my project regularly in the case that someone would eventually see it (and decide to roast me and my code). That being said, the real breakthrough came after I started posting about my app on Reddit, Discord and other online forums. People started opening issues, suggesting improvements and even sending pull requests. Suddenly, it wasn’t my project anymore - it became our project. The community helped me shape the roadmap, catch bugs and add features I wouldn’t have thought of alone, and took my app in an amazing direction I never would've thought of myself. 3. Focus on Design and Experience, Not Just Code A lot of open-source tools look like developer experiments - especially the project my app was initially based off of, kana pro (yes, you can google "kana pro" - it's a real website, and it's very ugly). I wanted my app to feel like a polished product - something a beginner could open and instantly understand, and also appreciate the beauty of the app's minimalist, aesthetic design. That meant obsessing over: Smooth animations and feedback loops Clean typography and layout Accessibility and mobile-first design I treated UX like part of the core functionality, not an afterthought - and users notice. Of course, the design is still far from perfect, but most users praise our unique, streamlined, no-frills approach and simplicity in terms of UI. 4. Build in Public (and Be Genuine About It) I regularly shared progress on Reddit, Discord, and a few Japanese-learning communities - not as ads, but as updates from a passionate learner. Even though I got downvoted and hated on dozens of times, people still responded to my authenticity. I wasn’t selling anything. I was just sharing something I built out of love for the language and for coding. Eventually, that transparency built trust and word-of-mouth growth that no paid marketing campaign could buy. 5. Community > Marketing My app's community has been everything. They’ve built
features, written guides, designed UI ideas and helped test new builds. A few things that helped nurture that: Creating a welcoming Discord (for learners and devs) Merging community PRs very fast Giving proper credit and showcasing contributors When people feel ownership and like they are not just the users, but the active developers of the app too, they don’t just use your app - they grow and develop it with you. 6. Keep It Free, Keep It Real The project remains completely open-source and free. No paywalls, no account sign-ups, no downloads (it's a in-browser web app, not a downloadable app store app, which a lot of users liked), no “pro” tiers or ads. That’s partly ideological - but also practical. People trust projects that stay true to their purpose. Final Thoughts Building my app has taught me more about software, design, and community than any college course ever could, even as I'm still going through college. For me, it’s been one hell of a grind; a very rewarding and, at times, confusing grind, but still. If you’re thinking of starting your own open-source project, here’s my advice: Build what you need first, not what others need. Ship early. Care about design and people. Stay consistent - it's hard to describe how many countless nights I had coding in bed at night with zero feedback, zero users and zero output, and yet I kept going because I just believed that what I'm building isn't useless and people may like and come to use it eventually. And most importantly: enjoy the process. <!-- SC_ON --> submitted by /u/tentoumushy (https://www.reddit.com/user/tentoumushy)
[link] (https://github.com/lingdojo/kana-dojo) [comments] (https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/)
[link] (https://github.com/lingdojo/kana-dojo) [comments] (https://www.reddit.com/r/programming/comments/1pix2ud/how_i_cultivated_an_opensource_platform_for/)
Driving 3D scenes in Blender with React
https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/
submitted by /u/roman01la (https://www.reddit.com/user/roman01la)
[link] (https://romanliutikov.com/blog/driving-3d-scenes-in-blender-with-react) [comments] (https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/)
https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/
submitted by /u/roman01la (https://www.reddit.com/user/roman01la)
[link] (https://romanliutikov.com/blog/driving-3d-scenes-in-blender-with-react) [comments] (https://www.reddit.com/r/programming/comments/1pj0rur/driving_3d_scenes_in_blender_with_react/)
Announcing ReScript 12
https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/
<!-- SC_OFF -->ReScript 12 arrives with a redesigned build toolchain, a modular runtime, and a wave of ergonomic language features. New features include: - New Build System - Improved Standard Library - Operator Improvements - Dict Literals and Dict Pattern Matching - Nested Record Types - Variant Pattern Spreads - JSX Preserve Mode - Function-Level Directives - Regex Literals - Experimental let? Syntax <!-- SC_ON --> submitted by /u/BeamMeUpBiscotti (https://www.reddit.com/user/BeamMeUpBiscotti)
[link] (https://renoscript-lang.org/blog/release-12-0-0/) [comments] (https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/)
https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/
<!-- SC_OFF -->ReScript 12 arrives with a redesigned build toolchain, a modular runtime, and a wave of ergonomic language features. New features include: - New Build System - Improved Standard Library - Operator Improvements - Dict Literals and Dict Pattern Matching - Nested Record Types - Variant Pattern Spreads - JSX Preserve Mode - Function-Level Directives - Regex Literals - Experimental let? Syntax <!-- SC_ON --> submitted by /u/BeamMeUpBiscotti (https://www.reddit.com/user/BeamMeUpBiscotti)
[link] (https://renoscript-lang.org/blog/release-12-0-0/) [comments] (https://www.reddit.com/r/programming/comments/1pj34s7/announcing_renoscript_12/)
Rust in the Linux kernel is officially here to stay
https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/
submitted by /u/NYPuppy (https://www.reddit.com/user/NYPuppy)
[link] (https://lwn.net/Articles/1049831/) [comments] (https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/)
https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/
submitted by /u/NYPuppy (https://www.reddit.com/user/NYPuppy)
[link] (https://lwn.net/Articles/1049831/) [comments] (https://www.reddit.com/r/programming/comments/1pj586l/rust_in_the_linux_kernel_is_officially_here_to/)
Go 1.26 package: runtime/secret -- zeros out registers and memory after running a function run in secret mode
https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/
submitted by /u/self (https://www.reddit.com/user/self)
[link] (https://antonz.org/accepted/runtime-secret/) [comments] (https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/)
https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/
submitted by /u/self (https://www.reddit.com/user/self)
[link] (https://antonz.org/accepted/runtime-secret/) [comments] (https://www.reddit.com/r/programming/comments/1pj5v86/go_126_package_runtimesecret_zeros_out_registers/)
COM Like a Bomb: Rust Outlook Add-in
https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/
<!-- SC_OFF -->A short write-up on implementing a COM integration for Outlook in Rust. <!-- SC_ON --> submitted by /u/urandomd (https://www.reddit.com/user/urandomd)
[link] (https://tritium.legal/blog/outlook) [comments] (https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/)
https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/
<!-- SC_OFF -->A short write-up on implementing a COM integration for Outlook in Rust. <!-- SC_ON --> submitted by /u/urandomd (https://www.reddit.com/user/urandomd)
[link] (https://tritium.legal/blog/outlook) [comments] (https://www.reddit.com/r/programming/comments/1pj6huh/com_like_a_bomb_rust_outlook_addin/)
Reverse Engineering Malicious Visual Studio Code Extension DarkGPT
https://www.reddit.com/r/programming/comments/1pj7gqn/reverse_engineering_malicious_visual_studio_code/
<!-- SC_OFF -->Malicious extensions are lurking in the Visual Studio Code marketplace. In this case, we discover and analyze DarkGPT, a Visual Studio Code extension that exploits DLL hijacking to load malicious code through a signed Windows executable. The payload appears to impact only Windows machines. Known malicious extensions: EffetMer.darkgpt BigBlack.codo-ai ozz3dev.bitcoin-auto-trading Malicious code in open source packages are not new. However, there is an interesting technique in this sample. The attackers leveraged a signed Windows executable (Lightshot.exe) as a trusted host process to deliver a malicious DLL (Lightshot.dll) loaded by the exe by default. Blog link: https://safedep.io/dark-gpt-vscode-malicious-extension/ <!-- SC_ON --> submitted by /u/N1ghtCod3r (https://www.reddit.com/user/N1ghtCod3r)
[link] (https://safedep.io/dark-gpt-vscode-malicious-extension/) [comments] (https://www.reddit.com/r/programming/comments/1pj7gqn/reverse_engineering_malicious_visual_studio_code/)
https://www.reddit.com/r/programming/comments/1pj7gqn/reverse_engineering_malicious_visual_studio_code/
<!-- SC_OFF -->Malicious extensions are lurking in the Visual Studio Code marketplace. In this case, we discover and analyze DarkGPT, a Visual Studio Code extension that exploits DLL hijacking to load malicious code through a signed Windows executable. The payload appears to impact only Windows machines. Known malicious extensions: EffetMer.darkgpt BigBlack.codo-ai ozz3dev.bitcoin-auto-trading Malicious code in open source packages are not new. However, there is an interesting technique in this sample. The attackers leveraged a signed Windows executable (Lightshot.exe) as a trusted host process to deliver a malicious DLL (Lightshot.dll) loaded by the exe by default. Blog link: https://safedep.io/dark-gpt-vscode-malicious-extension/ <!-- SC_ON --> submitted by /u/N1ghtCod3r (https://www.reddit.com/user/N1ghtCod3r)
[link] (https://safedep.io/dark-gpt-vscode-malicious-extension/) [comments] (https://www.reddit.com/r/programming/comments/1pj7gqn/reverse_engineering_malicious_visual_studio_code/)
Why write engineering blogs?
https://www.reddit.com/r/programming/comments/1pja0sd/why_write_engineering_blogs/
<!-- SC_OFF -->Responses from antirez, Charity Majors, Jeff Atwood, Gunnar Morling, Eric Lippert, Glauber Costa, Thorsten Ball... <!-- SC_ON --> submitted by /u/swdevtest (https://www.reddit.com/user/swdevtest)
[link] (https://writethatblog.substack.com/p/why-write-engineering-blogs) [comments] (https://www.reddit.com/r/programming/comments/1pja0sd/why_write_engineering_blogs/)
https://www.reddit.com/r/programming/comments/1pja0sd/why_write_engineering_blogs/
<!-- SC_OFF -->Responses from antirez, Charity Majors, Jeff Atwood, Gunnar Morling, Eric Lippert, Glauber Costa, Thorsten Ball... <!-- SC_ON --> submitted by /u/swdevtest (https://www.reddit.com/user/swdevtest)
[link] (https://writethatblog.substack.com/p/why-write-engineering-blogs) [comments] (https://www.reddit.com/r/programming/comments/1pja0sd/why_write_engineering_blogs/)
Call for Papers: 17th International Conference on Computational Creativity (ICCC'26) | June 29 to July 03, 2026
https://www.reddit.com/r/programming/comments/1pjboc5/call_for_papers_17th_international_conference_on/
submitted by /u/ICCCConf-Publicity (https://www.reddit.com/user/ICCCConf-Publicity)
[link] (https://computationalcreativity.net/iccc26/full-papers) [comments] (https://www.reddit.com/r/programming/comments/1pjboc5/call_for_papers_17th_international_conference_on/)
https://www.reddit.com/r/programming/comments/1pjboc5/call_for_papers_17th_international_conference_on/
submitted by /u/ICCCConf-Publicity (https://www.reddit.com/user/ICCCConf-Publicity)
[link] (https://computationalcreativity.net/iccc26/full-papers) [comments] (https://www.reddit.com/r/programming/comments/1pjboc5/call_for_papers_17th_international_conference_on/)
How we built single pass efficient faceted search inside PostgreSQL.
https://www.reddit.com/r/programming/comments/1pjebuz/how_we_built_single_pass_efficient_faceted_search/
<!-- SC_OFF -->We just updated `pg_search` to support faceted search 👀 It uses a custom window function, hooking the planner and using a custom scan so that all the work (search and aggregation) gets pushed down into a single pass of our BM25 index (which is based on Tantivy). Since the index has a columnar component, we can compute counts efficiently and return them as JSON alongside the ranked results. <!-- SC_ON --> submitted by /u/jamesgresql (https://www.reddit.com/user/jamesgresql)
[link] (https://www.paradedb.com/blog/faceting) [comments] (https://www.reddit.com/r/programming/comments/1pjebuz/how_we_built_single_pass_efficient_faceted_search/)
https://www.reddit.com/r/programming/comments/1pjebuz/how_we_built_single_pass_efficient_faceted_search/
<!-- SC_OFF -->We just updated `pg_search` to support faceted search 👀 It uses a custom window function, hooking the planner and using a custom scan so that all the work (search and aggregation) gets pushed down into a single pass of our BM25 index (which is based on Tantivy). Since the index has a columnar component, we can compute counts efficiently and return them as JSON alongside the ranked results. <!-- SC_ON --> submitted by /u/jamesgresql (https://www.reddit.com/user/jamesgresql)
[link] (https://www.paradedb.com/blog/faceting) [comments] (https://www.reddit.com/r/programming/comments/1pjebuz/how_we_built_single_pass_efficient_faceted_search/)
Computation of Discrete Logarithms in Prime Fields (Gaussian Integers Method)
https://www.reddit.com/r/programming/comments/1pjf5xy/computation_of_discrete_logarithms_in_prime/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/computation-of-discrete-logarithms-gaussian-eisenstein) [comments] (https://www.reddit.com/r/programming/comments/1pjf5xy/computation_of_discrete_logarithms_in_prime/)
https://www.reddit.com/r/programming/comments/1pjf5xy/computation_of_discrete_logarithms_in_prime/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/computation-of-discrete-logarithms-gaussian-eisenstein) [comments] (https://www.reddit.com/r/programming/comments/1pjf5xy/computation_of_discrete_logarithms_in_prime/)
The 7 finalists in the XPRIZE Quantum Applications competition
https://www.reddit.com/r/programming/comments/1pjgrvs/the_7_finalists_in_the_xprize_quantum/
submitted by /u/donutloop (https://www.reddit.com/user/donutloop)
[link] (https://blog.google/technology/research/google-gesda-xprize-quantum-applications-finalists/) [comments] (https://www.reddit.com/r/programming/comments/1pjgrvs/the_7_finalists_in_the_xprize_quantum/)
https://www.reddit.com/r/programming/comments/1pjgrvs/the_7_finalists_in_the_xprize_quantum/
submitted by /u/donutloop (https://www.reddit.com/user/donutloop)
[link] (https://blog.google/technology/research/google-gesda-xprize-quantum-applications-finalists/) [comments] (https://www.reddit.com/r/programming/comments/1pjgrvs/the_7_finalists_in_the_xprize_quantum/)
I analyzed 500 freelance jobs in Q4 2025. How the "Junior Specialist" is growing
https://www.reddit.com/r/programming/comments/1pjgtnz/i_analyzed_500_freelance_jobs_in_q4_2025_how_the/
<!-- SC_OFF -->I scraped data from 500 completed contracts on major freelance platforms (Upwork/Toptal) from November 2025 to see what’s going on and I found some interesting stuff. My Findings: Pure "Frontend" is a race to the bottom: Simple React/HTML/CSS jobs have plummeted in value ($20 – 40/hr) because AI generates UI too well. The "Integration" Premium: The highest paying junior-accessible roles ($80+/hr) are now "Glue Code" jobs. Connecting OpenAI API to Airtable, Stripe to Discord. The "Agentic" Shift: Businesses want Agents that run autonomously 24/7. The "Stack" has changed:
If you are building a portfolio in late 2025 to get hired, and you are building a "To-Do List" or a "Weather App," or even grinding leetcode, please stop. Recruiters and Clients want to see: Headless Browsers: (Playwright/Puppeteer) for data gathering. Vector DBs: (Pinecone/Weaviate) for RAG apps. Webhooks: Handling real-time data events. I dive deeper into this on my Medium article about the specific projects that are converting in 2025/26, including a Python snippet for a "Lead Gen Bot" that you can use to find your first client. <!-- SC_ON --> submitted by /u/Peach_Baker (https://www.reddit.com/user/Peach_Baker)
[link] (https://medium.com/@jameshugo598/the-junior-dev-isnt-dead-it-just-became-a-junior-specialists-role-6ef1a0e3d910) [comments] (https://www.reddit.com/r/programming/comments/1pjgtnz/i_analyzed_500_freelance_jobs_in_q4_2025_how_the/)
https://www.reddit.com/r/programming/comments/1pjgtnz/i_analyzed_500_freelance_jobs_in_q4_2025_how_the/
<!-- SC_OFF -->I scraped data from 500 completed contracts on major freelance platforms (Upwork/Toptal) from November 2025 to see what’s going on and I found some interesting stuff. My Findings: Pure "Frontend" is a race to the bottom: Simple React/HTML/CSS jobs have plummeted in value ($20 – 40/hr) because AI generates UI too well. The "Integration" Premium: The highest paying junior-accessible roles ($80+/hr) are now "Glue Code" jobs. Connecting OpenAI API to Airtable, Stripe to Discord. The "Agentic" Shift: Businesses want Agents that run autonomously 24/7. The "Stack" has changed:
If you are building a portfolio in late 2025 to get hired, and you are building a "To-Do List" or a "Weather App," or even grinding leetcode, please stop. Recruiters and Clients want to see: Headless Browsers: (Playwright/Puppeteer) for data gathering. Vector DBs: (Pinecone/Weaviate) for RAG apps. Webhooks: Handling real-time data events. I dive deeper into this on my Medium article about the specific projects that are converting in 2025/26, including a Python snippet for a "Lead Gen Bot" that you can use to find your first client. <!-- SC_ON --> submitted by /u/Peach_Baker (https://www.reddit.com/user/Peach_Baker)
[link] (https://medium.com/@jameshugo598/the-junior-dev-isnt-dead-it-just-became-a-junior-specialists-role-6ef1a0e3d910) [comments] (https://www.reddit.com/r/programming/comments/1pjgtnz/i_analyzed_500_freelance_jobs_in_q4_2025_how_the/)
Premature optimization is the root of all evil, so is ignoring scale (mental model)
https://www.reddit.com/r/programming/comments/1pjiexo/premature_optimization_is_the_root_of_all_evil_so/
submitted by /u/dmp0x7c5 (https://www.reddit.com/user/dmp0x7c5)
[link] (https://l.perspectiveship.com/re-scale) [comments] (https://www.reddit.com/r/programming/comments/1pjiexo/premature_optimization_is_the_root_of_all_evil_so/)
https://www.reddit.com/r/programming/comments/1pjiexo/premature_optimization_is_the_root_of_all_evil_so/
submitted by /u/dmp0x7c5 (https://www.reddit.com/user/dmp0x7c5)
[link] (https://l.perspectiveship.com/re-scale) [comments] (https://www.reddit.com/r/programming/comments/1pjiexo/premature_optimization_is_the_root_of_all_evil_so/)
EventSQL: events over SQL
https://www.reddit.com/r/programming/comments/1pjvjqh/eventsql_events_over_sql/
<!-- SC_OFF -->Events, and messages more broadly, are a battle-tested way of component to component, process to process, and/or application to application communication. In this approach, when something has happened, we publish an associated event. In general, events should inform us that something has happened. Related, there are Commands that request something more directly from another, not specified, process; they might as well be called a certain type of Events, but let's not split hair over semantics here. With Commands, it is mostly not that something has happened, but that something should happen as a result of command publication. Events are a pretty neat and handy way of having decoupled communication. The problem is that in most cases, if we do not publish them in-memory, inside a single process, there must be an additional component running on our infrastructure that provides this functionality. There are a slew of them; Apache Kafka, RabbitMQ, Apache Pulsar, Amazon SQS, Amazon SNS and Google Cloud Pub/Sub being the most widely used examples. Some of them are self-hosted and then we must have an expertise in hosting, configuring, monitoring and maintaining them, investing additional time and resources into these activities. Others are paid services - we tradeoff money for time and accept additional dependency on chosen service provider. In any case, we must give up on something - money, time or both. What if we were able to just use a type of SQL database already managed on our infrastructure to build a scalable Events Platform on top of it? That is exactly what I did with the EventSQL. All it requires is access to to an SQL database or databases. Below are the performance numbers it was able to handle, running on Postgres 16 instance, then three - 16 GB of memory and 8 CPUs (AMD) each. Single Postgres db - 16 GB MEM, 8 CPUs Publishing 1 200 000 events took 67.11s, which means 17 881 per second rate Consuming 1 200 000 events took 74.004s, which means 16 215 per second rate Three Postgres dbs - 16 GB MEM, 8 CPUs each Publishing 3 600 000 events took 66.448s, which means 54 177 per second rate Consuming 3 600 000 events took 78.118s, which means 46 083 per second rate <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://binaryigor.com/events-over-sql.html) [comments] (https://www.reddit.com/r/programming/comments/1pjvjqh/eventsql_events_over_sql/)
https://www.reddit.com/r/programming/comments/1pjvjqh/eventsql_events_over_sql/
<!-- SC_OFF -->Events, and messages more broadly, are a battle-tested way of component to component, process to process, and/or application to application communication. In this approach, when something has happened, we publish an associated event. In general, events should inform us that something has happened. Related, there are Commands that request something more directly from another, not specified, process; they might as well be called a certain type of Events, but let's not split hair over semantics here. With Commands, it is mostly not that something has happened, but that something should happen as a result of command publication. Events are a pretty neat and handy way of having decoupled communication. The problem is that in most cases, if we do not publish them in-memory, inside a single process, there must be an additional component running on our infrastructure that provides this functionality. There are a slew of them; Apache Kafka, RabbitMQ, Apache Pulsar, Amazon SQS, Amazon SNS and Google Cloud Pub/Sub being the most widely used examples. Some of them are self-hosted and then we must have an expertise in hosting, configuring, monitoring and maintaining them, investing additional time and resources into these activities. Others are paid services - we tradeoff money for time and accept additional dependency on chosen service provider. In any case, we must give up on something - money, time or both. What if we were able to just use a type of SQL database already managed on our infrastructure to build a scalable Events Platform on top of it? That is exactly what I did with the EventSQL. All it requires is access to to an SQL database or databases. Below are the performance numbers it was able to handle, running on Postgres 16 instance, then three - 16 GB of memory and 8 CPUs (AMD) each. Single Postgres db - 16 GB MEM, 8 CPUs Publishing 1 200 000 events took 67.11s, which means 17 881 per second rate Consuming 1 200 000 events took 74.004s, which means 16 215 per second rate Three Postgres dbs - 16 GB MEM, 8 CPUs each Publishing 3 600 000 events took 66.448s, which means 54 177 per second rate Consuming 3 600 000 events took 78.118s, which means 46 083 per second rate <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://binaryigor.com/events-over-sql.html) [comments] (https://www.reddit.com/r/programming/comments/1pjvjqh/eventsql_events_over_sql/)
Sectigo’s Wrongful Revocation of RustDesk’s EV Certificate: A Concerning Precedent for the Software Security Ecosystem
https://www.reddit.com/r/programming/comments/1pjsviw/sectigos_wrongful_revocation_of_rustdesks_ev/
submitted by /u/open-trade (https://www.reddit.com/user/open-trade)
[link] (https://github.com/rustdesk/rustdesk/discussions/13771) [comments] (https://www.reddit.com/r/programming/comments/1pjsviw/sectigos_wrongful_revocation_of_rustdesks_ev/)
https://www.reddit.com/r/programming/comments/1pjsviw/sectigos_wrongful_revocation_of_rustdesks_ev/
submitted by /u/open-trade (https://www.reddit.com/user/open-trade)
[link] (https://github.com/rustdesk/rustdesk/discussions/13771) [comments] (https://www.reddit.com/r/programming/comments/1pjsviw/sectigos_wrongful_revocation_of_rustdesks_ev/)
Finding broken migrations with Bisect
https://www.reddit.com/r/programming/comments/1pjvtlv/finding_broken_migrations_with_bisect/
submitted by /u/that_guy_iain (https://www.reddit.com/user/that_guy_iain)
[link] (https://iain.rocks/blog/2025/12/11/finding-broken-migrations-with-bisect) [comments] (https://www.reddit.com/r/programming/comments/1pjvtlv/finding_broken_migrations_with_bisect/)
https://www.reddit.com/r/programming/comments/1pjvtlv/finding_broken_migrations_with_bisect/
submitted by /u/that_guy_iain (https://www.reddit.com/user/that_guy_iain)
[link] (https://iain.rocks/blog/2025/12/11/finding-broken-migrations-with-bisect) [comments] (https://www.reddit.com/r/programming/comments/1pjvtlv/finding_broken_migrations_with_bisect/)
Getting Buy-In: Overcoming Larman's Law • Allen Holub
https://www.reddit.com/r/programming/comments/1pjx4h8/getting_buyin_overcoming_larmans_law_allen_holub/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/UAlumfwmcwY) [comments] (https://www.reddit.com/r/programming/comments/1pjx4h8/getting_buyin_overcoming_larmans_law_allen_holub/)
https://www.reddit.com/r/programming/comments/1pjx4h8/getting_buyin_overcoming_larmans_law_allen_holub/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/UAlumfwmcwY) [comments] (https://www.reddit.com/r/programming/comments/1pjx4h8/getting_buyin_overcoming_larmans_law_allen_holub/)