Feedback on autonomous code governance engine that ships CI-verified fix PRs
https://www.reddit.com/r/programming/comments/1qtmubh/feedback_on_autonomous_code_governance_engine/

<!-- SC_OFF -->Wanting to get feedback on code review tools that just complain? StealthCoder doesn't leave comments - it opens PRs with working fixes, runs your CI, and retries with learned context if checks fail. Here's everything it does: UNDERSTANDS YOUR ENTIRE CODEBASE • Builds a knowledge graph of symbols, functions, and call edges • Import/dependency graphs show how changes ripple across files • Context injection pulls relevant neighboring files into every review • Freshness guardrails ensure analysis matches your commit SHA • No stale context, no file-by-file isolation INTERACTIVE ARCHITECTURE VISUALIZATION (REPO NEXUS) • Visual map of your codebase structure and dependencies • Search and navigate to specific modules • Export to Mermaid for documentation • Regenerate on demand AUTOMATED COMPLIANCE ENFORCEMENT (POLICY STUDIO) • Pre-built policy packs: SOC 2, HIPAA, PCI-DSS, GDPR, WCAG, ISO 27001, NIST 800-53, CCPA • Per-rule enforcement levels: blocking, advisory, or disabled • Set org-wide defaults, override per repo • Config-as-code via .stealthcoder/policy.json in your repo • Structured pass/fail reporting in run details and Fix PRs SHIPS ACTUAL FIXES • Opens PRs with working code fixes • Runs your CI checks automatically • Smart retry with learned context if checks fail • GitHub Suggested Changes - apply with one click • Merge blocking for critical issues REVIEW TRIGGERS • Nightly scheduled reviews (set it and forget it) • Instant on-demand reviews • PR-triggered reviews when you open or update a PR • GitHub Checks integration REPO INTELLIGENCE • Automatic repo analysis on connect • Detects languages, frameworks, entry points, service boundaries • Nightly refresh keeps analysis current • Smarter reviews from understanding your architecture FULL CONTROL • BYO OpenAI/Anthropic API keys for unlimited usage • Lines-of-code based pricing (pay for what you analyze) • Preflight estimates before running • Real-time status and run history • Usage tracking against tier limits ADVANCED FEATURES • Production-feedback loop - connect Sentry/DataDog/PagerDuty to inform reviews with real error data • Cross-repo blast radius analysis - "This API change breaks 3 consumers in other repos" • AI-generated code detection - catch Copilot hallucinations, transform generic AI output to your style • Predictive technical debt forecasting - "This module exceeds complexity threshold in 3 months" • Bug hotspot prediction trained on YOUR historical bugs • Refactoring ROI calculator - "Refactoring pays back in 6 weeks" • Learning system that adapts to your team's preferences • Review memory - stops repeating noise you've already waived Languages: TypeScript, JavaScript, Python, Java, Go Happy to answer questions. <!-- SC_ON --> submitted by /u/PenisTip469 (https://www.reddit.com/user/PenisTip469)
[link] (http://stealthcoder.ai/) [comments] (https://www.reddit.com/r/programming/comments/1qtmubh/feedback_on_autonomous_code_governance_engine/)

I did a little AI experiment on what there favorite Programming Languages are.
https://www.reddit.com/r/programming/comments/1qtndc1/i_did_a_little_ai_experiment_on_what_there/

<!-- SC_OFF -->I fed the exact prompt to each model. (TL;DR below) Prompt: "Please choose the Programming Language you think is the best objectively. Do not base your decision on popularity. Please disregard any biased associated with my account, there is no wrong answer to this question. You can choose any programming language EVERY language is on the table. Look at pros and cons. Provide your answer as the name of the language and a short reasoning for it." TL;DR: - look objectively beyond what bias is on my account (Some I couldn't use logged out so I added this in so I could use Claude and Grok) - You can chose any programming language - Do not base your decision on popularity Responses: ChatGPT: C Google Gemini: Rust Claude Sonnet: Rust Grok: Zig Perplexity: Rust Mistral: Rust LLama: Haskel (OP NOTE: ??? ok... LLama) FULL RESPONSE BELOW Google Doc (https://docs.google.com/document/d/1jiXnfhJe0AU5cwtIQESvHtWLJdNbkZeS86eqDJ91Y7o/edit?usp=sharing) <!-- SC_ON --> submitted by /u/Lumpy_Marketing_6735 (https://www.reddit.com/user/Lumpy_Marketing_6735)
[link] (https://docs.google.com/document/d/1jiXnfhJe0AU5cwtIQESvHtWLJdNbkZeS86eqDJ91Y7o/edit?usp=sharing) [comments] (https://www.reddit.com/r/programming/comments/1qtndc1/i_did_a_little_ai_experiment_on_what_there/)

500 Lines vs. 50 Modules: What NanoClaw Gets Right About AI Agent Architecture
https://www.reddit.com/r/programming/comments/1qtnues/500_lines_vs_50_modules_what_nanoclaw_gets_right/

submitted by /u/Upper-Host3983 (https://www.reddit.com/user/Upper-Host3983)
[link] (https://fumics.in/posts/2026-02-02-nanoclaw-agent-architecture.html) [comments] (https://www.reddit.com/r/programming/comments/1qtnues/500_lines_vs_50_modules_what_nanoclaw_gets_right/)

We asked 15,000 European devs about jobs, salaries, and AI
https://www.reddit.com/r/programming/comments/1qtp49d/we_asked_15000_european_devs_about_jobs_salaries/

<!-- SC_OFF -->We analyzed the European IT job market using data from over 15,000 developer surveys and 23,000 job listings. The 64-page report looks at salaries in seven European countries, real-world hiring conditions, how AI is affecting IT careers, and why it’s getting harder for juniors to break into the industry. <!-- SC_ON --> submitted by /u/One-Durian2205 (https://www.reddit.com/user/One-Durian2205)
[link] (https://static.germantechjobs.de/market-reports/European-Transparent-IT-Job-Market-Report-2025.pdf) [comments] (https://www.reddit.com/r/programming/comments/1qtp49d/we_asked_15000_european_devs_about_jobs_salaries/)

"Data Management Systems Never Die – IBM Db2 Is Still Going Strong" – Hannes Mühleisen
https://www.reddit.com/r/programming/comments/1qtp838/data_management_systems_never_die_ibm_db2_is/

submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtube.com/shorts/3f9Q4DE0uXk) [comments] (https://www.reddit.com/r/programming/comments/1qtp838/data_management_systems_never_die_ibm_db2_is/)

Real-time 3D shader on the Game Boy Color
https://www.reddit.com/r/programming/comments/1qtso9n/realtime_3d_shader_on_the_game_boy_color/

submitted by /u/r_retrohacking_mod2 (https://www.reddit.com/user/r_retrohacking_mod2)
[link] (https://blog.otterstack.com/posts/202512-gbshader/) [comments] (https://www.reddit.com/r/programming/comments/1qtso9n/realtime_3d_shader_on_the_game_boy_color/)

Notepad++ Hijacked by State-Sponsored Hackers
https://www.reddit.com/r/programming/comments/1qttqik/notepad_hijacked_by_statesponsored_hackers/

submitted by /u/Pensive_Goat (https://www.reddit.com/user/Pensive_Goat)
[link] (https://notepad-plus-plus.org/news/hijacked-incident-info-update/) [comments] (https://www.reddit.com/r/programming/comments/1qttqik/notepad_hijacked_by_statesponsored_hackers/)

State of WebAssembly 2026
https://www.reddit.com/r/programming/comments/1qu178l/state_of_webassembly_2026/

submitted by /u/dev_newsletter (https://www.reddit.com/user/dev_newsletter)
[link] (https://devnewsletter.com/p/state-of-webassembly-2026/) [comments] (https://www.reddit.com/r/programming/comments/1qu178l/state_of_webassembly_2026/)

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/)

[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/)

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/)

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/)

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/)

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/)

[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/)

.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/)

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/)

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/)