A Supabase misconfiguration exposed every API key on Moltbook's 770K-agent platform. Two SQL statements would have prevented it
https://www.reddit.com/r/programming/comments/1qu1ek1/a_supabase_misconfiguration_exposed_every_api_key/
submitted by /u/rdizzy1234 (https://www.reddit.com/user/rdizzy1234)
[link] (https://www.telos-ai.org/blog/moltbook-security-nightmare) [comments] (https://www.reddit.com/r/programming/comments/1qu1ek1/a_supabase_misconfiguration_exposed_every_api_key/)
https://www.reddit.com/r/programming/comments/1qu1ek1/a_supabase_misconfiguration_exposed_every_api_key/
submitted by /u/rdizzy1234 (https://www.reddit.com/user/rdizzy1234)
[link] (https://www.telos-ai.org/blog/moltbook-security-nightmare) [comments] (https://www.reddit.com/r/programming/comments/1qu1ek1/a_supabase_misconfiguration_exposed_every_api_key/)
[kubernetes] Multiple issues in ingress-nginx
https://www.reddit.com/r/programming/comments/1qu4joa/kubernetes_multiple_issues_in_ingressnginx/
submitted by /u/ieyberg (https://www.reddit.com/user/ieyberg)
[link] (https://seclists.org/oss-sec/2026/q1/140) [comments] (https://www.reddit.com/r/programming/comments/1qu4joa/kubernetes_multiple_issues_in_ingressnginx/)
https://www.reddit.com/r/programming/comments/1qu4joa/kubernetes_multiple_issues_in_ingressnginx/
submitted by /u/ieyberg (https://www.reddit.com/user/ieyberg)
[link] (https://seclists.org/oss-sec/2026/q1/140) [comments] (https://www.reddit.com/r/programming/comments/1qu4joa/kubernetes_multiple_issues_in_ingressnginx/)
Surviving the Streaming Dungeon with Kafka Queues
https://www.reddit.com/r/programming/comments/1qu56yj/surviving_the_streaming_dungeon_with_kafka_queues/
submitted by /u/rionmonster (https://www.reddit.com/user/rionmonster)
[link] (https://rion.io/2026/02/02/surviving-the-streaming-dungeon-with-kafka-queues/) [comments] (https://www.reddit.com/r/programming/comments/1qu56yj/surviving_the_streaming_dungeon_with_kafka_queues/)
https://www.reddit.com/r/programming/comments/1qu56yj/surviving_the_streaming_dungeon_with_kafka_queues/
submitted by /u/rionmonster (https://www.reddit.com/user/rionmonster)
[link] (https://rion.io/2026/02/02/surviving-the-streaming-dungeon-with-kafka-queues/) [comments] (https://www.reddit.com/r/programming/comments/1qu56yj/surviving_the_streaming_dungeon_with_kafka_queues/)
Functional Programming Bits in Python
https://www.reddit.com/r/programming/comments/1qu574q/functional_programming_bits_in_python/
submitted by /u/Martynoas (https://www.reddit.com/user/Martynoas)
[link] (https://martynassubonis.substack.com/p/functional-programming-bits-in-python) [comments] (https://www.reddit.com/r/programming/comments/1qu574q/functional_programming_bits_in_python/)
https://www.reddit.com/r/programming/comments/1qu574q/functional_programming_bits_in_python/
submitted by /u/Martynoas (https://www.reddit.com/user/Martynoas)
[link] (https://martynassubonis.substack.com/p/functional-programming-bits-in-python) [comments] (https://www.reddit.com/r/programming/comments/1qu574q/functional_programming_bits_in_python/)
A reactive runtime where execution semantics are user-defined
https://www.reddit.com/r/programming/comments/1qu5sy0/a_reactive_runtime_where_execution_semantics_are/
<!-- SC_OFF -->I’m working on a small runtime that handles dependency tracking and re-execution.
What each node actually does is defined in user code via providers. <!-- SC_ON --> submitted by /u/Final-Shirt-8410 (https://www.reddit.com/user/Final-Shirt-8410)
[link] (https://github.com/creact-labs/creact) [comments] (https://www.reddit.com/r/programming/comments/1qu5sy0/a_reactive_runtime_where_execution_semantics_are/)
https://www.reddit.com/r/programming/comments/1qu5sy0/a_reactive_runtime_where_execution_semantics_are/
<!-- SC_OFF -->I’m working on a small runtime that handles dependency tracking and re-execution.
What each node actually does is defined in user code via providers. <!-- SC_ON --> submitted by /u/Final-Shirt-8410 (https://www.reddit.com/user/Final-Shirt-8410)
[link] (https://github.com/creact-labs/creact) [comments] (https://www.reddit.com/r/programming/comments/1qu5sy0/a_reactive_runtime_where_execution_semantics_are/)
Your Career Ladder is Rewarding the Wrong Behavior
https://www.reddit.com/r/programming/comments/1qu6t8s/your_career_ladder_is_rewarding_the_wrong_behavior/
<!-- SC_OFF -->Every engineering organization has a hero. They are the firefighter. The one who thrives under pressure, who can dive into a production-down incident at 3 AM and, through a combination of deep system knowledge and sheer brilliance, bring the system back to life. They are rewarded for it. They get the bonuses, the promotions, and the reputation as a "go-to" person. And in celebrating them, we are creating a culture that is destined to remain on fire. For every visible firefighter, there is an invisible fire preventer. This is the engineer who spends a month on a thankless, complex refactoring of a legacy service. Their work doesn't result in a new feature on the roadmap. Their success is silent—it's the catastrophic outage that doesn't happen six months from now. Their reward is to be overlooked in the next promotion cycle because their "impact" wasn't as visible as the hero who saved the day. This is a perverse incentive, and we, as managers, created it. Our performance review systems are fundamentally biased towards visible, reactive work over invisible, proactive work. We are great at measuring things we can easily count: features shipped, tickets closed, incidents resolved. We don't have a column on our spreadsheet for "catastrophes averted." As a result, we create a career ladder that implicitly encourages engineers to let things smolder, knowing the reward for putting out the eventual blaze is greater than the reward for ensuring there's no fire in the first place. It's time to change what we measure. "Impact" cannot be a synonym for "visible activity." Real impact is the verifiable elimination of future work and risk. The engineer who automates a flaky, manual deployment step hasn't just closed a ticket; they have verifiably improved the Lead Time for Changes for every single developer on the team, forever. That is massive, compounding impact. The engineer who refactors a high-churn, bug-prone module hasn't just "cleaned up code"; they have measurably reduced the Change Failure Rate for an entire domain of the business. That is a direct reduction in business risk. We need to start rewarding the architects of fireproof buildings, not just the most skilled firefighters. This requires a conscious, data-driven effort to find and celebrate the invisible work. It means using tools that can quantify the risk of a module before it fails, and then tracking the reduction of that risk as a first-class measure of an engineer's contribution. So the question to ask yourself in your next performance calibration is a hard one: Are we promoting the people who are best at navigating our broken system, or are we promoting the people who are actually fixing it? <!-- SC_ON --> submitted by /u/3sc2002 (https://www.reddit.com/user/3sc2002)
[link] (https://blog.3squaredcircles.com/) [comments] (https://www.reddit.com/r/programming/comments/1qu6t8s/your_career_ladder_is_rewarding_the_wrong_behavior/)
https://www.reddit.com/r/programming/comments/1qu6t8s/your_career_ladder_is_rewarding_the_wrong_behavior/
<!-- SC_OFF -->Every engineering organization has a hero. They are the firefighter. The one who thrives under pressure, who can dive into a production-down incident at 3 AM and, through a combination of deep system knowledge and sheer brilliance, bring the system back to life. They are rewarded for it. They get the bonuses, the promotions, and the reputation as a "go-to" person. And in celebrating them, we are creating a culture that is destined to remain on fire. For every visible firefighter, there is an invisible fire preventer. This is the engineer who spends a month on a thankless, complex refactoring of a legacy service. Their work doesn't result in a new feature on the roadmap. Their success is silent—it's the catastrophic outage that doesn't happen six months from now. Their reward is to be overlooked in the next promotion cycle because their "impact" wasn't as visible as the hero who saved the day. This is a perverse incentive, and we, as managers, created it. Our performance review systems are fundamentally biased towards visible, reactive work over invisible, proactive work. We are great at measuring things we can easily count: features shipped, tickets closed, incidents resolved. We don't have a column on our spreadsheet for "catastrophes averted." As a result, we create a career ladder that implicitly encourages engineers to let things smolder, knowing the reward for putting out the eventual blaze is greater than the reward for ensuring there's no fire in the first place. It's time to change what we measure. "Impact" cannot be a synonym for "visible activity." Real impact is the verifiable elimination of future work and risk. The engineer who automates a flaky, manual deployment step hasn't just closed a ticket; they have verifiably improved the Lead Time for Changes for every single developer on the team, forever. That is massive, compounding impact. The engineer who refactors a high-churn, bug-prone module hasn't just "cleaned up code"; they have measurably reduced the Change Failure Rate for an entire domain of the business. That is a direct reduction in business risk. We need to start rewarding the architects of fireproof buildings, not just the most skilled firefighters. This requires a conscious, data-driven effort to find and celebrate the invisible work. It means using tools that can quantify the risk of a module before it fails, and then tracking the reduction of that risk as a first-class measure of an engineer's contribution. So the question to ask yourself in your next performance calibration is a hard one: Are we promoting the people who are best at navigating our broken system, or are we promoting the people who are actually fixing it? <!-- SC_ON --> submitted by /u/3sc2002 (https://www.reddit.com/user/3sc2002)
[link] (https://blog.3squaredcircles.com/) [comments] (https://www.reddit.com/r/programming/comments/1qu6t8s/your_career_ladder_is_rewarding_the_wrong_behavior/)
Predicting Math.random() in Firefox using Z3 SMT-solver
https://www.reddit.com/r/programming/comments/1qu8bh6/predicting_mathrandom_in_firefox_using_z3/
submitted by /u/kyivenergo (https://www.reddit.com/user/kyivenergo)
[link] (https://yurichev.com/blog/xorshift/) [comments] (https://www.reddit.com/r/programming/comments/1qu8bh6/predicting_mathrandom_in_firefox_using_z3/)
https://www.reddit.com/r/programming/comments/1qu8bh6/predicting_mathrandom_in_firefox_using_z3/
submitted by /u/kyivenergo (https://www.reddit.com/user/kyivenergo)
[link] (https://yurichev.com/blog/xorshift/) [comments] (https://www.reddit.com/r/programming/comments/1qu8bh6/predicting_mathrandom_in_firefox_using_z3/)
Why In-House Education Matters Now
https://www.reddit.com/r/programming/comments/1qu8syx/why_inhouse_education_matters_now/
submitted by /u/Technical_Fly5479 (https://www.reddit.com/user/Technical_Fly5479)
[link] (https://github.com/FrederikLaursenSW/software-blog/tree/master/why-in-house-education-matters-now) [comments] (https://www.reddit.com/r/programming/comments/1qu8syx/why_inhouse_education_matters_now/)
https://www.reddit.com/r/programming/comments/1qu8syx/why_inhouse_education_matters_now/
submitted by /u/Technical_Fly5479 (https://www.reddit.com/user/Technical_Fly5479)
[link] (https://github.com/FrederikLaursenSW/software-blog/tree/master/why-in-house-education-matters-now) [comments] (https://www.reddit.com/r/programming/comments/1qu8syx/why_inhouse_education_matters_now/)
[Humor] A Field Guide to the Wildly Inaccurate Story Point
https://www.reddit.com/r/programming/comments/1qu94m2/humor_a_field_guide_to_the_wildly_inaccurate/
<!-- SC_OFF -->Here, on the vast plains of the Q3 roadmap, a remarkable ritual is about to unfold. The engineering tribe has gathered around the glow of the digital watering hole for the ceremony known as Sprint Planning. It is here that we can observe one of the most mysterious and misunderstood creatures in the entire corporate ecosystem: the Story Point. For decades, management scientists have mistaken this complex organism for a simple unit of time or effort. This is a grave error. The Story Point is not a number; it is a complex social signal, a display of dominance, a cry for help, or a desperate act of camouflage. After years of careful observation, we have classified several distinct species. 1. The Optimistic Two-Pointer (Estimatus Minimus) A small, deceptively placid creature, often identified by its deceptively simple ticket description. Its native call is, "Oh, that's trivial, it's just a small UI tweak." The Two-Pointer appears harmless, leading the tribe to believe it can be captured with minimal effort. However, it is the primary prey of the apex predator known as "Unforeseen Complexity." More often than not, the Two-Pointer reveals its true, monstrous form mid-sprint, devouring the hopes of the team and leaving behind a carcass of broken promises. 2. The Defensive Eight-Pointer (Fibonacci Maximus) This is not an estimate; it is a territorial display. The Eight-Pointer puffs up its chest, inflates its scope, and stands as a formidable warning to any Product Manager who might attempt to introduce scope creep. Its large size is a form of threat posturing, communicating not "this will take a long time," but "do not approach this ticket with your 'quick suggestions' or you will be gored." It is a protective measure, evolved to defend a developer's most precious resource: their sanity. 3. The Ambiguous Five-Pointer (Puntus Medius) The chameleon of the estimation world. The Five-Pointer is the physical embodiment of a shrug. It is neither confidently small nor defensively large. It is a signal of pure, unadulterated uncertainty. A developer who offers a Five-Pointer is not providing an estimate; they are casting a vote for "I have no idea, and I am afraid to commit." It survives by blending into the middle of the backlog, hoping to be overlooked. 4. The Mythical One-Pointer (Unicornis Simplex) A legendary creature, whose existence is the subject of much debate among crypto-zoologists of Agile. Sightings are incredibly rare. The legend describes a task so perfectly understood, so devoid of hidden dependencies, and so utterly simple that it can be captured and completed in a single afternoon. Most senior engineers believe it to be a myth, a story told to junior developers to give them hope. Conclusion: Our research indicates that the Story Point has very little to do with the actual effort required to complete a task. It is a complex language of risk, fear, and social negotiation, practiced by a tribe that is being forced to navigate a dark, unmapped territory. The entire, elaborate ritual of estimation is a coping mechanism for a fundamental lack of visibility. They are, in essence, guessing the size of a shadow without ever being allowed to see the object casting it. <!-- SC_ON --> submitted by /u/3sc2002 (https://www.reddit.com/user/3sc2002)
[link] (https://www.3squaredcircles.com/) [comments] (https://www.reddit.com/r/programming/comments/1qu94m2/humor_a_field_guide_to_the_wildly_inaccurate/)
https://www.reddit.com/r/programming/comments/1qu94m2/humor_a_field_guide_to_the_wildly_inaccurate/
<!-- SC_OFF -->Here, on the vast plains of the Q3 roadmap, a remarkable ritual is about to unfold. The engineering tribe has gathered around the glow of the digital watering hole for the ceremony known as Sprint Planning. It is here that we can observe one of the most mysterious and misunderstood creatures in the entire corporate ecosystem: the Story Point. For decades, management scientists have mistaken this complex organism for a simple unit of time or effort. This is a grave error. The Story Point is not a number; it is a complex social signal, a display of dominance, a cry for help, or a desperate act of camouflage. After years of careful observation, we have classified several distinct species. 1. The Optimistic Two-Pointer (Estimatus Minimus) A small, deceptively placid creature, often identified by its deceptively simple ticket description. Its native call is, "Oh, that's trivial, it's just a small UI tweak." The Two-Pointer appears harmless, leading the tribe to believe it can be captured with minimal effort. However, it is the primary prey of the apex predator known as "Unforeseen Complexity." More often than not, the Two-Pointer reveals its true, monstrous form mid-sprint, devouring the hopes of the team and leaving behind a carcass of broken promises. 2. The Defensive Eight-Pointer (Fibonacci Maximus) This is not an estimate; it is a territorial display. The Eight-Pointer puffs up its chest, inflates its scope, and stands as a formidable warning to any Product Manager who might attempt to introduce scope creep. Its large size is a form of threat posturing, communicating not "this will take a long time," but "do not approach this ticket with your 'quick suggestions' or you will be gored." It is a protective measure, evolved to defend a developer's most precious resource: their sanity. 3. The Ambiguous Five-Pointer (Puntus Medius) The chameleon of the estimation world. The Five-Pointer is the physical embodiment of a shrug. It is neither confidently small nor defensively large. It is a signal of pure, unadulterated uncertainty. A developer who offers a Five-Pointer is not providing an estimate; they are casting a vote for "I have no idea, and I am afraid to commit." It survives by blending into the middle of the backlog, hoping to be overlooked. 4. The Mythical One-Pointer (Unicornis Simplex) A legendary creature, whose existence is the subject of much debate among crypto-zoologists of Agile. Sightings are incredibly rare. The legend describes a task so perfectly understood, so devoid of hidden dependencies, and so utterly simple that it can be captured and completed in a single afternoon. Most senior engineers believe it to be a myth, a story told to junior developers to give them hope. Conclusion: Our research indicates that the Story Point has very little to do with the actual effort required to complete a task. It is a complex language of risk, fear, and social negotiation, practiced by a tribe that is being forced to navigate a dark, unmapped territory. The entire, elaborate ritual of estimation is a coping mechanism for a fundamental lack of visibility. They are, in essence, guessing the size of a shadow without ever being allowed to see the object casting it. <!-- SC_ON --> submitted by /u/3sc2002 (https://www.reddit.com/user/3sc2002)
[link] (https://www.3squaredcircles.com/) [comments] (https://www.reddit.com/r/programming/comments/1qu94m2/humor_a_field_guide_to_the_wildly_inaccurate/)
.net maui vs flutter
https://www.reddit.com/r/programming/comments/1qui6w2/net_maui_vs_flutter/
submitted by /u/Alexis542 (https://www.reddit.com/user/Alexis542)
[link] (https://www.reddit.com/r/dotnetMAUI/comments/1dzbit4/new_app_choose_between_flutter_or_net_maui/lcflgij/) [comments] (https://www.reddit.com/r/programming/comments/1qui6w2/net_maui_vs_flutter/)
https://www.reddit.com/r/programming/comments/1qui6w2/net_maui_vs_flutter/
submitted by /u/Alexis542 (https://www.reddit.com/user/Alexis542)
[link] (https://www.reddit.com/r/dotnetMAUI/comments/1dzbit4/new_app_choose_between_flutter_or_net_maui/lcflgij/) [comments] (https://www.reddit.com/r/programming/comments/1qui6w2/net_maui_vs_flutter/)
Rust Coreutils Continues Working Toward 100% GNU Compatibility, Proving Trolls Wrong
https://www.reddit.com/r/programming/comments/1qui7bq/rust_coreutils_continues_working_toward_100_gnu/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://archive.ph/CAMO5) [comments] (https://www.reddit.com/r/programming/comments/1qui7bq/rust_coreutils_continues_working_toward_100_gnu/)
https://www.reddit.com/r/programming/comments/1qui7bq/rust_coreutils_continues_working_toward_100_gnu/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://archive.ph/CAMO5) [comments] (https://www.reddit.com/r/programming/comments/1qui7bq/rust_coreutils_continues_working_toward_100_gnu/)
Sharing a toolkit to Batch Rename files and folders.
https://www.reddit.com/r/programming/comments/1qum8iq/sharing_a_toolkit_to_batch_rename_files_and/
<!-- SC_OFF -->Designed for the Pipeline: Rename Pro is a lightweight, high-performance companion tool built for professionals who cannot afford naming errors. Whether you are managing thousands of PBR textures, localized game assets, or complex production dailies, Rename Pro provides a stable, non-destructive environment to rename on the fly. Sequential Padding: Intelligent decimal padding (e.g., 001, 0001) for clean asset sorting. Real-Time Feedback: All changes to Prefix, Suffix, and Find/Replace logic update instantly in the preview list. Zero-Bloat Performance: Optimized to handle 50,000+ items with zero UI lag—perfect for massive asset libraries. Safety Measures: Includes a robust Undo system and duplicate path warnings to maintain folder integrity. <!-- SC_ON --> submitted by /u/iPEMiC (https://www.reddit.com/user/iPEMiC)
[link] (https://3dlakour.itch.io/rename-pro-10-stable-release-for-studio-indie-pipelines) [comments] (https://www.reddit.com/r/programming/comments/1qum8iq/sharing_a_toolkit_to_batch_rename_files_and/)
https://www.reddit.com/r/programming/comments/1qum8iq/sharing_a_toolkit_to_batch_rename_files_and/
<!-- SC_OFF -->Designed for the Pipeline: Rename Pro is a lightweight, high-performance companion tool built for professionals who cannot afford naming errors. Whether you are managing thousands of PBR textures, localized game assets, or complex production dailies, Rename Pro provides a stable, non-destructive environment to rename on the fly. Sequential Padding: Intelligent decimal padding (e.g., 001, 0001) for clean asset sorting. Real-Time Feedback: All changes to Prefix, Suffix, and Find/Replace logic update instantly in the preview list. Zero-Bloat Performance: Optimized to handle 50,000+ items with zero UI lag—perfect for massive asset libraries. Safety Measures: Includes a robust Undo system and duplicate path warnings to maintain folder integrity. <!-- SC_ON --> submitted by /u/iPEMiC (https://www.reddit.com/user/iPEMiC)
[link] (https://3dlakour.itch.io/rename-pro-10-stable-release-for-studio-indie-pipelines) [comments] (https://www.reddit.com/r/programming/comments/1qum8iq/sharing_a_toolkit_to_batch_rename_files_and/)
OpenAI's Codex App Wants to Replace Your IDE. I'm Not Sure It Should.
https://www.reddit.com/r/programming/comments/1qumh9t/openais_codex_app_wants_to_replace_your_ide_im/
submitted by /u/Upper-Host3983 (https://www.reddit.com/user/Upper-Host3983)
[link] (https://fumics.in/posts/2026-02-03-codex-app-death-of-ide.html) [comments] (https://www.reddit.com/r/programming/comments/1qumh9t/openais_codex_app_wants_to_replace_your_ide_im/)
https://www.reddit.com/r/programming/comments/1qumh9t/openais_codex_app_wants_to_replace_your_ide_im/
submitted by /u/Upper-Host3983 (https://www.reddit.com/user/Upper-Host3983)
[link] (https://fumics.in/posts/2026-02-03-codex-app-death-of-ide.html) [comments] (https://www.reddit.com/r/programming/comments/1qumh9t/openais_codex_app_wants_to_replace_your_ide_im/)
A browser benchmark that actually uses all your CPU/GPU cores
https://www.reddit.com/r/programming/comments/1qumlzn/a_browser_benchmark_that_actually_uses_all_your/
<!-- SC_OFF -->Hey, everyone. I felt that the current benchmarks are too synthetic. That’s why I have built SpeedPower.run (http://speedpower.run/) as a 'maximum compute' test that runs six concurrent benchmarks: Javascript (multi-core JS processing), Exchange (worker communication), and five distinct AI inference models. We are unique in the market because we simultaneously run different AI models built on popular stacks (TensorFlow.js and Transformers.js v3) to get a true measure of system-wide concurrency. Roast our methodology or share your score. We're here for the feedback. <!-- SC_ON --> submitted by /u/Kirk_GC (https://www.reddit.com/user/Kirk_GC)
[link] (https://speedpower.run/?ref=reddit-programming-1) [comments] (https://www.reddit.com/r/programming/comments/1qumlzn/a_browser_benchmark_that_actually_uses_all_your/)
https://www.reddit.com/r/programming/comments/1qumlzn/a_browser_benchmark_that_actually_uses_all_your/
<!-- SC_OFF -->Hey, everyone. I felt that the current benchmarks are too synthetic. That’s why I have built SpeedPower.run (http://speedpower.run/) as a 'maximum compute' test that runs six concurrent benchmarks: Javascript (multi-core JS processing), Exchange (worker communication), and five distinct AI inference models. We are unique in the market because we simultaneously run different AI models built on popular stacks (TensorFlow.js and Transformers.js v3) to get a true measure of system-wide concurrency. Roast our methodology or share your score. We're here for the feedback. <!-- SC_ON --> submitted by /u/Kirk_GC (https://www.reddit.com/user/Kirk_GC)
[link] (https://speedpower.run/?ref=reddit-programming-1) [comments] (https://www.reddit.com/r/programming/comments/1qumlzn/a_browser_benchmark_that_actually_uses_all_your/)
How to write Effective Prompts like code artifacts, not questions?
https://www.reddit.com/r/programming/comments/1quna8w/how_to_write_effective_prompts_like_code/
<!-- SC_OFF -->Prompts should be written like Java artifacts, not questions. For example: A prompt behaves like a method signature: it defines inputs and expected output Context behaves like a Jira ticket: business + technical requirements Role assignment is similar to annotations: it changes behavior Constraints work like NotNull/ validations: they limit execution scope Another big improvement come from avoiding “do everything at once” prompts and switching to step-based prompts (analysis-> plan-> execution-> explanation). That alone makes outputs far more reliable for debugging, refactoring, and architectural discussions. The detailed article on "How to write Effective Prompt using code Analogy (https://javatechonline.com/effective-ai-prompts-for-java-developers-and-architects/)" is explaining this Java-centric way of writing AI prompts, with real examples from Spring Boot and backend development. <!-- SC_ON --> submitted by /u/erdsingh24 (https://www.reddit.com/user/erdsingh24)
[link] (https://javatechonline.com/effective-ai-prompts-for-java-developers-and-architects/) [comments] (https://www.reddit.com/r/programming/comments/1quna8w/how_to_write_effective_prompts_like_code/)
https://www.reddit.com/r/programming/comments/1quna8w/how_to_write_effective_prompts_like_code/
<!-- SC_OFF -->Prompts should be written like Java artifacts, not questions. For example: A prompt behaves like a method signature: it defines inputs and expected output Context behaves like a Jira ticket: business + technical requirements Role assignment is similar to annotations: it changes behavior Constraints work like NotNull/ validations: they limit execution scope Another big improvement come from avoiding “do everything at once” prompts and switching to step-based prompts (analysis-> plan-> execution-> explanation). That alone makes outputs far more reliable for debugging, refactoring, and architectural discussions. The detailed article on "How to write Effective Prompt using code Analogy (https://javatechonline.com/effective-ai-prompts-for-java-developers-and-architects/)" is explaining this Java-centric way of writing AI prompts, with real examples from Spring Boot and backend development. <!-- SC_ON --> submitted by /u/erdsingh24 (https://www.reddit.com/user/erdsingh24)
[link] (https://javatechonline.com/effective-ai-prompts-for-java-developers-and-architects/) [comments] (https://www.reddit.com/r/programming/comments/1quna8w/how_to_write_effective_prompts_like_code/)
I built a real-time multiplayer chess platform with Elo rankings, friend system, and game replays [Open Source]
https://www.reddit.com/r/programming/comments/1qunc53/i_built_a_realtime_multiplayer_chess_platform/
<!-- SC_OFF -->Hey everyone! 👋 I've been working on Play Chess - a modern, real-time chess platform where you can play with friends or other players online, completely free in your browser. Key Features: - ♟️ Real-time multiplayer powered by Socket.IO - 📊 Elo ranking system to track your skill level - 👥 Friend system - add friends and challenge them directly - 🎮 Game replays - review your moves and learn from your games - 📈 Player statistics - track your wins, losses, and performance - 🎵 Sound effects for moves, captures, and checks - 📱 Fully responsive - works on desktop and mobile Tech Stack: Built with Next.js 15, Express, Socket.IO, TypeScript, Prisma, PostgreSQL, and Tailwind CSS in a Turborepo monorepo. The project is open source (MIT License), so feel free to check it out, contribute, or use it as a learning resource! Optional Pro Membership supports development and unlocks a few extra features like direct challenges and a Pro badge. Would love to hear your feedback or suggestions! Happy to answer any questions about the implementation or features. GitHub: https://github.com/vijaysingh2219/play-chess <!-- SC_ON --> submitted by /u/bruh2219 (https://www.reddit.com/user/bruh2219)
[link] (https://github.com/vijaysingh2219/play-chess) [comments] (https://www.reddit.com/r/programming/comments/1qunc53/i_built_a_realtime_multiplayer_chess_platform/)
https://www.reddit.com/r/programming/comments/1qunc53/i_built_a_realtime_multiplayer_chess_platform/
<!-- SC_OFF -->Hey everyone! 👋 I've been working on Play Chess - a modern, real-time chess platform where you can play with friends or other players online, completely free in your browser. Key Features: - ♟️ Real-time multiplayer powered by Socket.IO - 📊 Elo ranking system to track your skill level - 👥 Friend system - add friends and challenge them directly - 🎮 Game replays - review your moves and learn from your games - 📈 Player statistics - track your wins, losses, and performance - 🎵 Sound effects for moves, captures, and checks - 📱 Fully responsive - works on desktop and mobile Tech Stack: Built with Next.js 15, Express, Socket.IO, TypeScript, Prisma, PostgreSQL, and Tailwind CSS in a Turborepo monorepo. The project is open source (MIT License), so feel free to check it out, contribute, or use it as a learning resource! Optional Pro Membership supports development and unlocks a few extra features like direct challenges and a Pro badge. Would love to hear your feedback or suggestions! Happy to answer any questions about the implementation or features. GitHub: https://github.com/vijaysingh2219/play-chess <!-- SC_ON --> submitted by /u/bruh2219 (https://www.reddit.com/user/bruh2219)
[link] (https://github.com/vijaysingh2219/play-chess) [comments] (https://www.reddit.com/r/programming/comments/1qunc53/i_built_a_realtime_multiplayer_chess_platform/)
Open Source security in spite of AI
https://www.reddit.com/r/programming/comments/1qurly9/open_source_security_in_spite_of_ai/
submitted by /u/kivarada (https://www.reddit.com/user/kivarada)
[link] (https://daniel.haxx.se/blog/2026/02/03/open-source-security-in-spite-of-ai/?utm_source=insidestack&utm_medium=social) [comments] (https://www.reddit.com/r/programming/comments/1qurly9/open_source_security_in_spite_of_ai/)
https://www.reddit.com/r/programming/comments/1qurly9/open_source_security_in_spite_of_ai/
submitted by /u/kivarada (https://www.reddit.com/user/kivarada)
[link] (https://daniel.haxx.se/blog/2026/02/03/open-source-security-in-spite-of-ai/?utm_source=insidestack&utm_medium=social) [comments] (https://www.reddit.com/r/programming/comments/1qurly9/open_source_security_in_spite_of_ai/)
Release of TURA
https://www.reddit.com/r/programming/comments/1quuknp/release_of_tura/
<!-- SC_OFF -->We’re excited to announce the first release of our coding book, Thinking, Understanding, and Reasoning in Algorithms (TURA). This book focuses on building deep intuition and structured thinking in algorithms, rather than just memorizing techniques and acts as a complement to the CSES Problem Set. Please do give it a read, contribute on GitHub, and share it with fellow programmers who you think would benefit from it. This is a work in progress non-profit, open-source initiative. https://github.com/T-U-R-A/tura-coding-book/releases <!-- SC_ON --> submitted by /u/Pure-Raccoon-4181 (https://www.reddit.com/user/Pure-Raccoon-4181)
[link] (https://github.com/T-U-R-A/tura-coding-book/releases) [comments] (https://www.reddit.com/r/programming/comments/1quuknp/release_of_tura/)
https://www.reddit.com/r/programming/comments/1quuknp/release_of_tura/
<!-- SC_OFF -->We’re excited to announce the first release of our coding book, Thinking, Understanding, and Reasoning in Algorithms (TURA). This book focuses on building deep intuition and structured thinking in algorithms, rather than just memorizing techniques and acts as a complement to the CSES Problem Set. Please do give it a read, contribute on GitHub, and share it with fellow programmers who you think would benefit from it. This is a work in progress non-profit, open-source initiative. https://github.com/T-U-R-A/tura-coding-book/releases <!-- SC_ON --> submitted by /u/Pure-Raccoon-4181 (https://www.reddit.com/user/Pure-Raccoon-4181)
[link] (https://github.com/T-U-R-A/tura-coding-book/releases) [comments] (https://www.reddit.com/r/programming/comments/1quuknp/release_of_tura/)
The Cost of Leaving a Software Rewrite “On the Table"
https://www.reddit.com/r/programming/comments/1qv0zz8/the_cost_of_leaving_a_software_rewrite_on_the/
submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://blog.planetargon.com/blog/entries/the-cost-of-leaving-a-software-rewrite-on-the-table) [comments] (https://www.reddit.com/r/programming/comments/1qv0zz8/the_cost_of_leaving_a_software_rewrite_on_the/)
https://www.reddit.com/r/programming/comments/1qv0zz8/the_cost_of_leaving_a_software_rewrite_on_the/
submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://blog.planetargon.com/blog/entries/the-cost-of-leaving-a-software-rewrite-on-the-table) [comments] (https://www.reddit.com/r/programming/comments/1qv0zz8/the_cost_of_leaving_a_software_rewrite_on_the/)
Sustainability in Software Development: Robby Russell on Tech Debt and Engineering Culture
https://www.reddit.com/r/programming/comments/1qv2kpa/sustainability_in_software_development_robby/
<!-- SC_OFF -->Recent guest appearance on Overcommitted <!-- SC_ON --> submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://overcommitted.dev/sustainability-in-software-development-robby-russell-on-tech-debt-and-engineering-culture/) [comments] (https://www.reddit.com/r/programming/comments/1qv2kpa/sustainability_in_software_development_robby/)
https://www.reddit.com/r/programming/comments/1qv2kpa/sustainability_in_software_development_robby/
<!-- SC_OFF -->Recent guest appearance on Overcommitted <!-- SC_ON --> submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://overcommitted.dev/sustainability-in-software-development-robby-russell-on-tech-debt-and-engineering-culture/) [comments] (https://www.reddit.com/r/programming/comments/1qv2kpa/sustainability_in_software_development_robby/)
How to deal with a Vibe Coding CEO and still keep everyone happy
https://www.reddit.com/r/programming/comments/1qv4nb5/how_to_deal_with_a_vibe_coding_ceo_and_still_keep/
submitted by /u/okawei (https://www.reddit.com/user/okawei)
[link] (https://ariso.ai/blog/dealing-with-a-vibe-coding-ceo) [comments] (https://www.reddit.com/r/programming/comments/1qv4nb5/how_to_deal_with_a_vibe_coding_ceo_and_still_keep/)
https://www.reddit.com/r/programming/comments/1qv4nb5/how_to_deal_with_a_vibe_coding_ceo_and_still_keep/
submitted by /u/okawei (https://www.reddit.com/user/okawei)
[link] (https://ariso.ai/blog/dealing-with-a-vibe-coding-ceo) [comments] (https://www.reddit.com/r/programming/comments/1qv4nb5/how_to_deal_with_a_vibe_coding_ceo_and_still_keep/)