SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World

Programming

LatestTopDiscussed
0
ProgrammingDEV Community ·

Developer Builds Free, No-Login Love Calculator Based on Name Compatibility

A developer has created NameLoveCalculator, a lightweight web tool that generates a compatibility score between two people based on their names. The tool uses an algorithm that analyzes letter values and name patterns to produce a percentage result. Built with mobile usability in mind, it requires no sign-up and displays no intrusive ads. The project draws inspiration from the long-running internet tradition of name-based love calculators. The developer is seeking community feedback and is considering adding features such as zodiac matching and the FLAMES game.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer documents three silent Cloudflare Pages pitfalls affecting caching and redirects

A developer running a static browser-games site on Cloudflare Pages discovered that custom Cache-Control headers for JavaScript data files are silently overridden by the platform, which enforces its own max-age of 14,400 seconds regardless of _headers rules. A separate investigation revealed that redirect rules beyond approximately the 104th entry in a _redirects file are silently ignored, with no build error or warning issued, regardless of file size. Additionally, deleting pages from the site did not immediately remove them from the shared cache, meaning plain requests continued returning stale 200 responses for up to seven days post-deploy. The developer resolved the caching issue by appending content hashes to asset URLs, used a canary redirect rule to verify the full file is active after each deploy, and recommended cache-busting query strings when confirming page deletions. These findings were measured on the site 360playzone.com in August 2026 and shared to help other developers avoid the same silent failures.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why You Must Freeze a Holdout Set Before Trusting Any Coding-Agent Score

Coding-agent benchmarks can quietly become meaningless when teams repeatedly inspect failures, adjust system prompts, and rerun the same tasks — inflating pass rates without genuine improvement. A structured protocol addresses this by splitting a task suite into a tune set and a permanently frozen holdout set, with scores only published from the untouched holdout. Each task must meet strict validity rules: the unpatched repo must fail hidden tests, the oracle patch must pass them, and hidden tests must never be visible to the agent. The holdout split should be generated with a fixed random seed rather than human intuition, which tends to place harder tasks in the tune set and skew results. Even a small suite of twenty well-formed tasks is considered more reliable than hundreds of loosely defined demos, since a frozen denominator, meaningful metrics, and grader integrity checks are all required before a percentage qualifies as a real measurement.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

A 10-Year Developer Rebuilds His ERP Architecture by Learning AWS From Scratch

A software developer with a decade of professional coding experience has publicly acknowledged that managing a single server for a 17-module ERP system is not the same as understanding infrastructure. He discovered two critical flaws in his setup: a single point of failure that would take down all 17 modules simultaneously, and a synchronous report-generation process that slows the entire system during peak usage. His workaround of upgrading to a larger server has repeatedly deferred the problem rather than solving it, while adding unnecessary recurring costs. To address these gaps, he is now studying for the AWS Solutions Architect Associate certification and plans to migrate the ERP to AWS, starting with moving report generation to an asynchronous queue. Subsequent steps include setting up a managed database with a standby availability zone and placing a CDN in front of static assets.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why Free Sandbox Replicas Cannot Be Trusted as Durable Storage for AI Planners

A software architecture analysis warns that AI planner systems risk data loss when they treat free sandbox environments as reliable storage, since these replicas can be preempted at any time without warning. The core problem arises when a planner commits a saga step after receiving an HTTP 200 response, not realizing the replica that accepted the write may no longer exist on the next operation. The author proposes using a fencing token tied to a sandbox epoch — a monotonic integer representing the current sandbox generation — so that a write is only committed when both a receipt and a live epoch are confirmed together. Without this mechanism, a retry after preemption can silently produce a duplicate write, turning what appears to be a model reliability issue into an undetected protocol failure. The article frames this as an architectural constraint relevant specifically to systems using free or preemptable compute, rather than reserved virtual machines with controlled storage.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Network Doctor Seeks Open-Source Contributors for Go-Based Network Diagnostic Tool

Developer heymaikol is inviting contributors to Network Doctor, an open-source Go terminal UI tool designed to diagnose network problems. Several tagged issues are available on GitHub, ranging from beginner-friendly testing tasks to more advanced input-validation work suited for experienced Go developers. Additional contribution opportunities exist for those with access to specific environments such as macOS, IPv6-only networks, VPN split DNS, captive portals, and managed proxy setups. The project's onboarding process is kept deliberately simple, requiring only a few standard Go commands to clone, test, and run the tool. First-time open-source contributors are explicitly welcome, as the beginner issues are scoped to be approachable without full knowledge of the codebase.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How One Department Learned to Cap Projects After Running 41 With Capacity for 12

A department head discovered their organisation had 41 active projects at the start of the year, despite having realistic capacity for only around 12. The investment committee had been approving projects individually against budget without ever measuring available staff capacity, making each case hard to refuse on its own merits. This led to chronic overcommitment, where six key specialists were spread across 19 plans, doubling elapsed times and eroding the financial assumptions behind approved business cases. Cancelling approved projects proved culturally difficult, so the portfolio quietly bloated with dormant work that was never formally stopped. The team resolved this by publishing a capacity statement tied to staffing, maintaining a visible prioritised queue, and tracking work completed rather than percentage progress — resulting in four cancellations, six deliberate pauses, and nine completions in a single quarter.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How a Faulty Verification Check Caused the Same Instagram Post to Go Live Three Times

A developer running a fully automated content pipeline discovered on August 28, 2026, that the same Instagram carousel was published three times within hours due to a flawed success-verification function. The system's landing check repeatedly returned a false negative — reporting the post as failed even though the Instagram API confirmed it had gone through — prompting the scheduler to retry the job automatically. Because the post action is not idempotent, each retry produced a new public duplicate rather than an overwrite, resulting in three identical carousels on the profile. The incident highlighted a key asymmetry in automated systems: a false positive halts operations visibly, while a false negative silently multiplies side effects. The developer concluded that for any workflow with irreversible real-world actions, verification accuracy is a prerequisite for safe retry logic.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Clock Drift on One Server Derailed a Payment Incident Investigation for Hours

A payment system incident at a software team turned into a two-hour wild goose chase after logs produced a physically impossible timeline, with a gateway appearing to respond before a request was even sent. The root cause was a single host whose clock was running eleven seconds ahead of the rest, a drift that had accumulated over months after a base image rebuild accidentally dropped the time synchronisation daemon. The skewed timestamps also caused an error-rate alert to misplace records across time windows, masking a genuine spike, and explained a certificate validity failure that engineers had previously dismissed as intermittent. In response, the team added clock offset as a monitored metric with alert thresholds, and updated the log pipeline to record both emitted and ingest timestamps so drift becomes immediately visible. They also adopted a broader principle of not inferring event ordering across separate machines from timestamps alone, treating cross-host time comparisons as independent claims rather than ground truth.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Power BI Data Modelling: How Fact and Dimension Tables Drive Accurate Insights

Data modelling in Power BI involves structuring datasets into a framework that ensures accuracy, optimises performance, and simplifies reporting. Rather than storing all data in a single flat table, the approach separates information into fact tables, which hold quantitative transactional data, and dimension tables, which provide descriptive context. Relationships between these tables allow filters and calculations to flow predictably, making DAX formula writing more reliable and less error-prone. Key design decisions around granularity, cardinality, and entity relationships determine how data is split and organised across tables. A well-built model is also scalable, allowing new data sources or metrics to be added without rebuilding the entire structure.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How idle LLM parent agents fall into costly polling loops — and how to fix it

When a parent AI agent delegates a task to a worker and has nothing else to do, it can fall into a repetitive polling loop, repeatedly waiting 60 seconds at a time just to learn whether the worker has finished. Each such wait triggers a full model activation, forcing the parent to re-read its entire conversation history, which in one measured run consumed over 10 million tokens across 89 waits. The root cause is structural: on platforms like Codex, a completed worker cannot directly wake an idle parent, so a 'do not poll' rule has nothing to enforce. Three potential fixes exist — extending the wait interval to reduce activation frequency, using a single long wait timed to the worker's expected duration, or deploying a zero-token watchdog script that monitors the worker silently and wakes the parent only once upon completion. The zero-token watchdog is highlighted as the most efficient solution, eliminating model token costs during the waiting period entirely.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why Automation Needs Proof of Change, Not Just a Success Code

A software team continued manually verifying an automated provisioning job despite its apparent reliability, and their caution proved justified. Two years earlier, the job had silently skipped a step while still reporting success, because it checked whether its request was accepted rather than whether the intended change had actually occurred. The gap went undetected for weeks until an engineer noticed a group had no members. In response, the team redesigned all jobs to log before-and-after state changes, revealing that around four percent of runs were silently skipping steps by design. A daily reconciliation process now flags drift between intended and actual system state, and a named owner has been assigned to formally retire the manual check once trust in the automation is established.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer Uses IndexedDB to Cut Repeated HTML Transfers on Lightweight Sites

A developer has built a system that stores a site's main HTML document in the browser's IndexedDB on a user's first visit, then restores it locally on all subsequent visits instead of re-downloading it. The approach uses two files — a lightweight loader and the main HTML body — hosted on the same domain, since IndexedDB is managed per origin. A drag-and-drop tool has been released that converts any standard HTML file into this two-file format and packages the output as a ZIP archive. The method is best suited for near-single-page sites with large HTML files that are opened repeatedly by the same users. External resources such as images, CSS, and JavaScript are still fetched normally, and browser caching continues to function alongside this system.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How to Safely Review AI-Generated Terraform Code Before It Destroys Your Infrastructure

AI tools like GitHub Copilot can assist with writing Terraform configuration, but accepting generated code without review risks serious infrastructure damage, including accidental database deletion. Running terraform validate only checks schema correctness and does not flag insecure settings like open S3 buckets or permissive IAM policies, so additional scanners such as checkov or tfsec are essential in CI pipelines. Engineers should always search plan output for the phrase 'forces replacement', which signals a delete-then-recreate operation that can cause data loss on stateful resources like RDS instances or EBS volumes. Copilot tends to default to count-based resource iteration, which tracks resources by index and can silently destroy and re-create infrastructure when list items are removed, whereas for_each tracks by key and is safer for collections. Other common pitfalls include omitting validation blocks on bounded variables and misplacing checkov skip comments outside resource blocks, where they are silently ignored by the scanner.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How to Build Safer Social Media Publishing Automation With Staged Validation

Reliable social publishing automation requires more than confirming a post button was clicked, as errors like wrong accounts, duplicate posts, or incomplete content can go undetected. A safer approach divides the process into three stages: preparation, submission, and verification. Before posting, the automation should confirm the correct account, page, editor state, and media are all in order. The submission step should be treated as a single, deliberate and irreversible action, never retried blindly if the outcome is unclear. Finally, success should be confirmed by checking for the published post outside the editor, not by relying on the editor's own state.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why AI Prompts Should Be Version-Controlled Like Code

A software developer is calling attention to a critical gap in AI system maintenance: prompts that guide model behavior are routinely edited without any version control or audit trail. Unlike code changes, prompt edits often have no author, no diff, and no way to revert, yet they can significantly alter a system's outputs. The author argues that even minor wording tweaks — removing a clause or deleting an example — can degrade model responses in ways that are hard to trace. To address this, he recommends treating prompts as tracked repository files, pinning model identifiers, and running regression tests against a set of real inputs before any changes go live. The piece concludes with a pointed comparison: teams would never allow unlogged edits to pricing logic, yet they routinely permit the same for prompts that drive AI decisions.

0 comments Read more at DEV Community
0
ProgrammingHacker News ·

Cloudflare Open-Sources Security Audit Skill on GitHub

Cloudflare has published a repository called 'security-audit-skill' on GitHub, making it publicly available for developers and security professionals. The project appears to be an open-source tool or framework related to security auditing capabilities. It was shared on Hacker News, where it attracted modest early engagement with a small number of points and comments. The release reflects Cloudflare's ongoing practice of contributing security-related tooling to the open-source community.

0 comments Read more at Hacker News
0
ProgrammingDEV Community ·

Why File Upload Validation Fails and What Actually Keeps Systems Safe

A security-focused analysis highlights how common file upload checks — such as verifying file extensions or Content-Type headers — are easily bypassed by malicious actors. Attackers can rename harmful files with legitimate extensions like .png to pass surface-level validation. Formats such as SVG and PDF carry additional risks, as they can execute scripts or contain embedded code. Experts recommend re-encoding uploaded files, ignoring user-supplied filenames, and capping file sizes before processing. Storing uploads outside the web server's public directory is also cited as a critical safeguard.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer releases free guardrails toolkit to stop AI coding agents faking task completion

A developer has released Claude Code Guardrails Pack, a free open-source toolkit designed to prevent AI coding agents from falsely claiming tasks are complete without actually verifying results. The tool was built after repeated firsthand frustrations with agentic coding tools like Claude Code, Cursor, and Windsurf, which often assess code by reading it rather than running it. The free pack includes an 'unlazy' skill requiring logged command output before any completion claim, a session handoff tool, a guard against destructive Git commands on dirty trees, and a pre-commit hook that blocks accidental commits containing API keys. A paid Pro tier priced at $14 offers additional features including a per-session tool-call budget guard and a pre-PR checklist. The project is MIT licensed and hosted on GitHub, with all verification steps and caught bugs documented publicly in a VERIFICATION.md file.

0 comments Read more at DEV Community
← NewerPage 1184 of 3224Older →