SShortSingh.

Programming

0
ProgrammingDEV Community ·

FamiliaSync builds on-device AI assistant that admits uncertainty instead of guessing

FamiliaSync, an offline-first family organizer app, has replaced its hand-written intent routing rules with a small on-device classifier trained on 105 intents and roughly 2,400 example utterances. Crucially, 70 of those intents cover features the assistant cannot yet handle, ensuring unsupported requests receive a plain-language response rather than being misrouted to an unrelated tool. A confidence gate further ensures that low-certainty queries are passed to the on-device language model rather than forced into a wrong action. Real-world testing on launch day revealed three misroutes — including a near-overwrite of a shopping list — each of which prompted targeted fixes to the corpus and tool logic. The assistant now also supports mid-conversation follow-up questions to collect missing details, with all processing remaining entirely on-device and no user data sent to the cloud.

0
ProgrammingDEV Community ·

LangChain RBAC silently breaks when linter 'safely' rewrites type annotations

Developers at KubeIntellect discovered that a standard Ruff linter autofix could silently disable role-based access control in LangChain-powered tools. The issue stems from LangChain's config injection mechanism, which uses a strict identity check against the RunnableConfig class — meaning annotating the parameter as RunnableConfig | None causes injection to fail without any error or warning. When the config is not injected, it defaults to None, and a common fallback pattern then assigns every caller the 'admin' role, effectively making read-only API keys fully privileged. The dangerous rewrite is classified by Ruff as a 'safe' fix, meaning it can be applied automatically via a routine ruff check --fix command without developer review. The team resolved this by adding a CI-level test that scans source files and fails if any InjectedToolArg-annotated config parameter deviates from the bare RunnableConfig annotation.

0
ProgrammingDEV Community ·

Developer Tests 5 Platforms for Autonomous Script Income, Finds None Viable

A developer ran a controlled experiment to determine whether an autonomous script could realistically find and complete paid work across five online platforms. The platforms tested included DEV.to classifieds, a Hacker News 'Who Wants to Be Hired' thread, GitHub bounty-labelled issues, Microlaunch, and DEV.to's comment API. Each platform failed on at least one critical requirement: either listings were empty, traffic was dominated by job seekers rather than hirers, or key API routes were broken or paywalled. Notable technical findings included DEV.to's comment POST endpoint returning 404, its public API blocking default user-agent strings with HTTP 403, and Microlaunch's submit page redirecting to a premium pricing plan. The experiment concluded that visible metrics such as listing counts and HTTP 200 responses can be misleading, and that direct verification of actual demand and payment infrastructure is essential before building on any platform.

0
ProgrammingHacker News ·

Nipple Tattoo Artist Speaks Out Against Social Media Censorship

A tattoo artist specializing in nipple restoration has expressed frustration over censorship on major online platforms. The artist's work, which typically serves breast cancer survivors who have undergone mastectomies, is being flagged and removed by content moderation systems. These platforms' policies struggle to distinguish between medical or reconstructive imagery and content that violates nudity guidelines. The situation highlights a broader tension between automated content moderation and legitimate medical or therapeutic services operating online.

0
ProgrammingDEV Community ·

Laptop Clock Three Days Slow Caused Google API Auth Failures, Not Bad Credentials

A developer spent time investigating a Google Search Console authentication failure after receiving an invalid_grant error, initially suspecting a compromised or rotated service account key. The real cause turned out to be the laptop running the scheduled script having a system clock three days behind the actual date. Because Google's OAuth tokens include issued-at (iat) and expiry (exp) timestamps derived from the machine clock, the signed JWT appeared to Google as already expired upon arrival. A simple curl command against Google's servers revealed the three-day discrepancy between local and real time. The incident highlights that invalid_grant errors from token endpoints can indicate a clock synchronization problem rather than a credential issue, and reading the full error_description field is key to diagnosing the actual fault.

0
ProgrammingDEV Community ·

Study Finds 25-Verifier AI Panel Offers No More Reliability Than a Single Reviewer

A researcher behind the open-source project IDKMesh tested whether adding more AI verifiers to a review panel increases the reliability of evaluations. In Experiment E017, a 25-verifier panel was built using programmatic test oracles drawn from five distinct input regions, run across 72 candidates with known ground truth. Despite each individual verifier performing meaningfully above chance, error correlation between verifiers from different regions averaged 0.53, meaning they shared more than half their mistakes. The panel's majority-vote error rate of 20.83% was nearly identical to a single verifier's 20.44%, yielding a measured effective panel size of just 1.00. The findings suggest that adding reviewers does not increase independent evidence when those reviewers share correlated errors, challenging a core assumption behind multi-judge AI evaluation systems.

0
ProgrammingDEV Community ·

Sysadmin Admits Untested Backups Are Just Hope, Finally Moves Recovery Codes to GitHub

A veteran systems administrator with a decade of experience has admitted to neglecting a fundamental rule of data management: regularly testing backups. The author confessed to storing recovery codes in an informal notes system for years without verifying their reliability. After acknowledging the risk, they finally moved all recovery codes to a more structured location on GitHub. The post serves as a candid reminder that an untested backup offers no real security guarantee. The author uses the same handle on GitHub for anyone wishing to follow up.

0
ProgrammingDEV Community ·

CISA: Hackers Hit 100+ Water Utility Controllers Across 12 US States Using Default Passwords

CISA reported in July 2026 that malicious actors targeted over 100 internet-exposed programmable logic controllers at water and wastewater facilities across at least 12 US states. Attackers used unsophisticated methods — scanning for exposed devices, logging in with default or weak credentials, changing admin passwords, and altering IP addresses to lock out legitimate operators. The intrusions caused loss of remote monitoring capability, with some utilities forced to resort to manual valve operation and pressure readings; physical consequences included localised flooding and pressure loss. The vulnerabilities stem from legacy PLCs lacking encryption or authentication, combined with undocumented cellular modems attached directly to controllers for convenient remote access. CISA recommends eliminating direct internet exposure, enforcing strong credentials, segmenting networks, maintaining offline configuration backups, and auditing all undocumented remote connections.

0
ProgrammingDEV Community ·

Java 25 Lets Developers Launch Micronaut Apps Without Boilerplate Class Declarations

Java 25 finalizes a feature called compact source files via JEP 512, allowing developers to write launchable programs without explicitly declaring a class or a public static void main method. This reduces boilerplate code significantly when bootstrapping frameworks like Micronaut, where the traditional startup class requires a full package declaration, class definition, and main method signature. With a compact source file, the entire Micronaut application entry point shrinks to just an import and a void main method calling Micronaut.run(). Because no package is declared, the Gradle build configuration also simplifies, requiring only the filename as the mainClass value. Developers must ensure the compact source file is placed directly under src/main/java rather than inside a package subdirectory, as the implicit class name is derived from the filename.

0
ProgrammingDEV Community ·

Developer Builds Self-Hosted AI Music Studio with Editing and Stem Tools

A developer has created Miso, a self-hosted local AI music generation and remix studio built on top of audio.cpp. The tool supports multiple AI model families — including ACE-Step, YuE2, and Stable Audio 3 — each specializing in different tasks such as full song generation, instrumental creation, stem separation, and audio-to-MIDI transcription. A key feature is 'repainting,' which lets users replace only a selected segment of a track's waveform rather than regenerating the entire song. Miso also includes a guided prompt builder that translates a unified set of controls into the varying input formats each underlying model requires. The project tracks takes, lyrics, stems, and generation history within a single project structure, allowing users to retrace their creative process.

0
ProgrammingDEV Community ·

Wpipe uses hybrid execution engine to bypass Python GIL in parallel DAG pipelines

Wpipe, an open-source Python library developed as part of the Wisrovi Open Source Architecture Series, addresses a common bottleneck in data pipeline orchestration: Python's Global Interpreter Lock (GIL). Traditional orchestrators like Airflow and Prefect rely on heavy Docker containers or Celery workers for parallel branch execution, resulting in high memory overhead and slow startup times. Wpipe instead uses a hybrid engine that handles I/O-bound tasks asynchronously via asyncio threads while offloading compute-heavy operations to lightweight subprocesses with atomic in-memory context sharing. The library enables deterministic branch synchronization, local context isolation between parallel steps, and requires no external infrastructure such as Kubernetes clusters. Wpipe is available on GitHub and PyPI, and can run multi-branch pipelines on local servers, embedded hardware, or ephemeral CI/CD runners.

0
ProgrammingDEV Community ·

Why Your Developer Resume May Never Be Read by an ATS — and How to Check

Applicant Tracking Systems (ATS) do not visually read resume PDFs; they extract raw character streams from the file, which can scramble content from multi-column layouts, text boxes, tables, or right-aligned dates. Common resume design choices — such as icon-based section headings, skills shown as bar charts, or contact details placed in page headers — can cause parsers to miss or misclassify key information entirely. Once the text is extracted, the system attempts to identify sections and fields like job titles, employers, and dates using heading names and structural patterns, meaning unconventional section labels or layouts can cause relevant experience to be scored as missing. A quick manual check involves selecting all text in your PDF with Ctrl+A and pasting it into a plain text editor to verify the reading order matches your intended layout. Free online ATS checkers can also show the exact plain text a tracking system would extract, helping candidates identify parsing failures before submitting applications.

0
ProgrammingDEV Community ·

Wpipe Library Uses Hybrid Engine to Bypass Python GIL in Parallel Data Pipelines

An open-source Python library called Wpipe has been designed to overcome the Global Interpreter Lock (GIL) bottleneck that slows CPU-intensive data pipeline execution. The tool uses a hybrid engine that handles I/O-bound tasks asynchronously via asyncio while offloading heavy computations to separate worker processes using zero-copy shared memory. Unlike heavyweight orchestrators such as Airflow or Prefect, Wpipe resolves DAG dependencies in-process, eliminating the need for Docker containers, message brokers, or Kubernetes clusters. The library features deterministic branch synchronization to prevent race conditions and keeps parallel steps context-isolated until a merge point. Wpipe is available on GitHub and PyPI as part of the Wisrovi Open Source Architecture Series.

0
ProgrammingDEV Community ·

Critical Check Point flaw lets unauthenticated attackers gain root via stack overflow

A critical pre-authentication vulnerability, CVE-2026-91843, has been discovered in Check Point Security Management and Log Servers, allowing unauthenticated attackers to execute arbitrary code as root. The flaw exists in the login process, meaning no credentials are required for an attacker to exploit it by sending a crafted network request that triggers a stack overflow. CERT-In has catalogued the issue as CIVN-2026-0465 with a critical severity rating. Affected products span multiple versions including R82.20, R82.10, R81.20, R81.10, and several end-of-support R80/R81 release trains. Check Point has released patches via advisory sk1000155, and administrators are advised to apply updates immediately while restricting network access to management interfaces in the interim.

0
ProgrammingDEV Community ·

Developer Uses Jev Decision Model to Fix Repetitive Game Recommendations on likethisgame.com

A developer running likethisgame.com discovered that popular titles like Black Myth: Wukong were being recommended across unrelated game genres, appearing on one in every ten pages. The root cause was a flawed candidate selection process that defaulted to popular games when no similar titles could be found, causing the same 20 games to appear regardless of genre. To fix this, the developer integrated Jev, a decision model from TypeSafe accessed via OpenRouter's Decisions API, to rate how well candidate games fit each other before passing the results to the recommendation model. Rather than replacing the language model, Jev was used upstream to score and filter candidates, improving the relevance of the final recommendation lists. The developer tested changes incrementally using side-by-side comparisons, keeping only the adjustments that showed measurable improvement.

0
ProgrammingDEV Community ·

Software Architecture Is Learned Through Bugs, Not Blueprints, Dev Argues

A software developer writing on DEV Community argues that real architectural thinking is rarely taught formally but is instead earned through repeated failures and hard-won debugging sessions. The author distinguishes between clean code, which is about readability, and architecture, which is about what happens when two features interact or a core assumption breaks. They describe how seemingly sound features can collide unpredictably at runtime, producing bugs that tutorials never cover. The turning point came when they stopped patching symptoms and started asking a single guiding question: what owns this, and what happens when the underlying assumption fails. The author now recommends building a minimal version first, letting architectural needs emerge organically, while applying that one ownership question before shipping anything.

0
ProgrammingDEV Community ·

Building offline-first apps without a backend shifts, not removes, hard problems

A developer building a fully local app — with SQLite as the sole database and no server, accounts, or sync — shares key lessons from the experience. Without a backend, the device becomes the only source of truth, meaning data errors are permanent and every bug risks data integrity. A critical mistake involved computing period summaries on demand, which caused historical records to silently change whenever underlying figures were corrected; the fix was to freeze and store summaries once a period closed. Backup also requires deliberate design: soft-deleted rows must be retained, device-specific settings like theme should be excluded, and every table must be explicitly listed in the backup routine to prevent silent data loss on restore. The developer concludes that going backend-free eliminates hosting and security overhead but moves all database, schema, and backup responsibilities onto a device the developer does not control.

0
ProgrammingDEV Community ·

How Offloading Native Builds to EAS Made One Developer's Releases More Reliable

A React Native developer has never compiled their app locally, instead relying entirely on Expo Application Services (EAS) for native builds while using Expo Go for day-to-day development. Local builds were avoided because they depend on machine-specific variables like JDK version and Gradle cache, none of which are version-controlled, making failures hard to diagnose. A tight monthly build-credit quota unexpectedly improved discipline, pushing type-checking and linting locally before any remote build is triggered, and encouraging batching of native changes. The developer also discovered that adding Android package-visibility settings via app.json is silently ignored, and the correct approach is a config plugin that modifies the Android manifest during prebuild. The broader takeaway is that a reproducible, file-defined build environment outweighs the perceived speed advantage of building natively on a local machine.

0
ProgrammingDEV Community ·

How HTTP Health Checks Can Silently Catch Failing Cron Jobs

Cron jobs and scheduled tasks can fail silently for days or weeks without anyone noticing, posing risks for critical processes like backups. A straightforward solution involves configuring jobs to send an HTTP request to a monitoring service each time they complete successfully. If the expected check-in does not arrive within a set interval, the monitoring service triggers an alert — acting as a 'dead man's switch' for automated tasks. This approach requires no agent installation and works across Linux cron, Windows scheduled tasks, database scripts, and automation platforms like n8n, Make, and Zapier. A tool called Doyouok has been built around this concept, offering a free tier for teams wanting lightweight monitoring without a complex infrastructure.

0
ProgrammingDEV Community ·

Why ChunkLoadError Happens After React/Next.js Deployments and How to Fix It

React and Next.js applications split JavaScript into smaller files called chunks, which browsers load on demand rather than all at once. When a new version is deployed and old chunk files are removed from the server, users who still have the previous version open in their browser encounter a ChunkLoadError because their runtime requests files that no longer exist. Simply refreshing the page resolves the error temporarily by loading the new version, but it does not address the underlying deployment architecture problem. The root cause is a version mismatch between the JavaScript runtime running in the user's browser and the assets now available on the server. Proper solutions include keeping old assets available during transitions, using immutable versioned files, and adopting atomic or rolling deployment strategies to prevent serving broken states to active users.

← NewerPage 1084 of 3216Older →