SShortSingh.

Programming

0
ProgrammingDEV Community ·

TWAP Distance Alone Is Not Enough to Build a Reliable Polymarket Strategy

A developer and quantitative researcher has outlined a framework for using Time-Weighted Average Price (TWAP) distance as a signal in automated Polymarket prediction-market trading. The core argument is that raw price deviation from a TWAP is insufficient on its own, as it cannot distinguish between mispricing, new information, liquidity gaps, or a lagging reference value. A more reliable approach involves normalizing the deviation against recent volatility, then layering in signal velocity, order-book depth, and execution conditions before acting. The framework also warns against treating large deviations as automatic mean-reversion opportunities, since the same observation can equally indicate that new information has arrived and the TWAP simply hasn't caught up. Validating outcomes — tracking whether the deviation contracted or expanded after a signal — is presented as essential to refining any distance-based trading strategy.

0
ProgrammingDEV Community ·

Operations veteran ships PromptSpend mobile app, shares hard lessons from store approvals to layout bugs

PromptSpend, an open-source LLM cost calculator built by a 15-year operations professional, is now live on both the Apple App Store and Google Play. The app lets users estimate AI feature costs across roughly 80 models from 12 providers by pasting a sample conversation and selecting expected traffic volumes. To ensure pricing accuracy, the app fetches a live catalog on launch rather than bundling a static file, refusing to calculate if cached data exceeds 24 hours old. All token counting is performed on-device with no user data uploaded, stored, or tied to any account or analytics identifier. The developer noted that store enrollment — including Apple's individual-to-organization conversion and Google Play's mandatory 14-day closed test with 12 testers — proved more time-consuming than the coding itself, advising others to budget weeks, not days, for that process.

0
ProgrammingDEV Community ·

How to Build a Private Local AI Coding Workstation on Any Budget in 2026

As cloud-based AI coding assistants grow costlier, developers are turning to private local setups to avoid subscription fees and protect client code. Even a mid-range machine with 16GB of system RAM and a basic GPU can run small 3B–8B parameter models for code completion, refactoring, and codebase queries without uploading data to external servers. Tools like Ollama and llama.cpp make it possible to query a local codebase directly from the terminal, with aggressive quantization keeping performance usable even on integrated graphics. Upgrading to a GPU with 12–16GB of VRAM unlocks larger 20B–32B quantized models capable of handling agentic coding loops with broader context. The guide recommends splitting tasks between a fast smaller model for inline completion and a slower, smarter model for chat and refactoring to balance latency and capability.

0
ProgrammingDEV Community ·

Cloudflare Adds Granular Controls to Separate AI Training from Search Indexing

Cloudflare has rolled out updated AI-crawler controls that allow website owners to block AI model training while still permitting search indexing, replacing its previous all-or-nothing 'Block AI Bots' toggle. The new system introduces three distinct policy categories — Search, Training, and Agent — giving publishers finer control over how automated bots interact with their content. A new default configuration, effective September 15, 2026, will block Training and Agent crawlers while keeping Search crawlers allowed. Cloudflare is also replacing its Managed Robots.txt feature with Bot Preference Sync, which automatically aligns a site's robots.txt file with its configured crawler policies to prevent conflicting signals. The update is designed to benefit ad-supported and content-driven sites that rely on organic search visibility but wish to opt out of contributing to AI training datasets.

0
ProgrammingDEV Community ·

Developer builds GitHub Action to display DEV.to follower count on profile README

A developer has completed a side project that uses a scheduled GitHub Actions workflow to automatically display their DEV.to follower count on their GitHub profile README. The project had been abandoned for nearly a year after repeated workflow failures, which generated daily failure notification emails. After revisiting the code, the developer fixed the issue by correcting an API call and removing redundant commented-out code, achieving the first successful run on attempt number 343. The working YAML configuration runs daily at midnight UTC, fetches follower data via the DEV.to API, and commits any changes to the README automatically. The developer has shared the full code publicly, advising others to store API keys as environment secrets rather than hardcoding them.

0
ProgrammingDEV Community ·

Supply Chain Breaches Hit 48% of Confirmed Incidents as Credential Relay Attacks Surge

The 2026 Verizon Data Breach Investigations Report found third-party involvement in nearly half of all confirmed breaches, a 60% year-over-year increase, while IBM's 2026 breach report found supplier-originated incidents take an average of 258 days to contain. A key mechanism driving these numbers is credential relay, where stolen credentials from one vendor are reused to compromise that vendor's downstream customers. In March 2026, attackers used Google Cloud Platform credentials harvested from the Salesloft Drift breach to infiltrate Telus Digital, ultimately exposing data from hundreds of companies. A separate August 2026 attack poisoned the LiteLLM API gateway, reaching roughly 2,500 organizations and exposing an estimated 195TB of password data within approximately 40 minutes. Security experts recommend treating vendor breach disclosures as immediate credential rotation triggers and maintaining a live inventory of SaaS integration credentials to reduce the window attackers exploit.

0
ProgrammingDEV Community ·

How NATS Leaf Nodes Solve MQTT Data Loss During WAN Outages at Scale

IoT devices publishing MQTT data to cloud brokers lose readings during WAN outages, a problem often discovered only weeks later when gaps appear in data logs. The two common fixes — QoS 1 persistent sessions and local Mosquitto brokers — both buffer data locally but create growing operational complexity as deployments scale to hundreds of sites. A key hidden cost is namespace drift, where different sites end up using inconsistent topic naming conventions, forcing engineers to maintain translation layers in the cloud. NATS offers an alternative via leaf nodes with JetStream enabled at each site, allowing devices to keep publishing on port 1883 while the site stores data locally and syncs with the hub when connectivity resumes. Unlike traditional bridging, this approach treats all sites as part of one network, so topic names remain consistent across every location without requiring configuration changes when new sites are added.

0
ProgrammingDEV Community ·

KDE Plasma crash loop after Kubuntu update traced to fontconfig race condition

A KDE Plasma crash loop was reported on Kubuntu 26.04 following a full system upgrade via the nala package manager. After rebooting, plasmashell entered a continuous crash cycle that persisted despite attempts to roll back to an older kernel, clear caches, and reinstall plasmashell and widgets. The root cause was identified as a fontconfig race condition triggered by the update. A fix was documented by Mišo Oroz for Zerolock on September 23, resolving the issue for affected users.

0
ProgrammingHacker News ·

Qualcomm Announces Linux Support for Snapdragon X2 Series Chips

Qualcomm has announced that Linux support is coming to its Snapdragon X2 series of processors. The announcement was made at the Snapdragon Summit, where the company also highlighted agentic AI capabilities for PCs. The news was shared via Qualcomm's official OnQ blog in September 2026. The development is significant for users and developers seeking to run Linux on Snapdragon X2-powered devices.

0
ProgrammingDEV Community ·

PDF vs CSV for Contract Reports: How to Choose and Alert Correctly

A technical analysis highlights the key differences between PDF and CSV formats for server-side contract report exports, arguing each serves a distinct consumer. PDF suits humans needing a stable, reviewable document, while CSV is better for analysts or systems processing structured row data. The article warns against treating both formats identically in monitoring dashboards, noting that queue depth alone is a poor alerting signal. Engineers are advised to estimate drain time from observed completion rates and page on sustained deadline risk or stalled progress rather than raw job counts. Producing both formats from the same immutable report snapshot, with shared batch identifiers and a verifiable manifest, is recommended to avoid costly reconciliation errors.

0
ProgrammingDEV Community ·

Five Common Causes Behind Most Moodle 5.1 to 5.2 Upgrade Failures

Developers upgrading Moodle from version 5.1 to 5.2 frequently encounter failures traced to five recurring technical issues. The most common problem is an incorrectly configured web server document root, as Moodle 5.1 and later require the server to point to the public/ subdirectory. Other frequent causes include missing r.php router configuration, an absent vendor/ directory requiring Composer to be run from the Moodle root, outdated plugins referencing deprecated Mustache class names, and stale caches that can be cleared via CLI or the admin panel. Experts recommend backing up code, moodledata, and the database before upgrading, and always testing on a staging copy of the site before applying changes to production.

0
ProgrammingHacker News ·

Mercury 2.5 LLM achieves 770 tokens per second generation speed

Mercury 2.5 is a large language model that has reached a generation speed of 770 tokens per second, according to data published on Artificial Analysis. This figure places it among the faster models currently being benchmarked on the platform. The milestone was noted by the Hacker News community, where the announcement attracted early discussion. Speed benchmarks like this are increasingly relevant as developers evaluate LLMs for latency-sensitive applications.

0
ProgrammingDEV Community ·

Kubernetes Architecture Explained: Control Plane, Worker Nodes and Core Components

Kubernetes (k8s) is an open-source container orchestration platform that automates deployment, scaling, self-healing, and load balancing of containerized applications across clusters. A Kubernetes cluster is divided into two main parts: the control plane, which manages overall cluster state, and worker nodes, where application workloads actually run. Key control plane components include the API server, etcd key-value store, scheduler, and controller manager, while worker nodes run the kubelet, kube-proxy, and a container runtime. Developers can explore these components locally without a cloud account using tools like Minikube, which simulates a full cluster on a personal machine. Running 'minikube start' spins up a single-node cluster where one machine acts as both control plane and worker node, allowing hands-on learning of Kubernetes internals.

0
ProgrammingDEV Community ·

Google Renames NotebookLM to Gemini Notebook, Deepens Workspace Integration

Google is rebranding NotebookLM as Gemini Notebook, with the new name and logo rolling out from July 16, 2026 across its interfaces. The rename brings the research and source-grounding tool more formally into the Gemini product family. Since January 27, 2026, users have been able to attach NotebookLM notebooks as grounded sources in Gemini chats, allowing responses to draw on a defined body of reference material. The updated product is available to Google Workspace customers, Workspace Individual subscribers, and personal Google account holders with existing NotebookLM access. Google notes that pricing, admin controls, and regional availability vary, so users are advised to check what features are enabled for their specific accounts.

0
ProgrammingHacker News ·

Cloudflare Adds Support for HTTP Vary Header in Its CDN Cache

Cloudflare has announced support for the HTTP Vary header, a long-neglected but important part of the HTTP specification. The Vary header tells caches to store different versions of a resource based on request attributes such as encoding or content type. Historically, CDNs have struggled or refused to implement Vary due to its complexity and potential for cache inefficiency. Cloudflare's implementation aims to handle this correctly, improving cache accuracy for content that varies by request headers. The update was detailed in a post on the Cloudflare Blog and has drawn attention from the developer community on Hacker News.

0
ProgrammingHacker News ·

The Bayeux Tapestry: A Norman Perspective on the 1066 Conquest

The Bayeux Tapestry is a medieval embroidered cloth depicting the events surrounding the Norman conquest of England in 1066. Historians have long noted that the tapestry presents the story largely from the perspective of the victorious Normans. As a piece of visual propaganda, it frames William the Conqueror's invasion as a justified claim to the English throne. Scholars continue to examine how its narrative choices reflect the political interests of those who commissioned it. The tapestry remains one of the most studied artifacts of medieval history, raising questions about bias in historical storytelling.

0
ProgrammingHacker News ·

Lab-Grown Meat Falls Short of Its Promised Revolution

A new Harper's Magazine investigation examines why the lab-grown meat industry has failed to deliver on its ambitious promises. The piece explores the significant gap between early hype surrounding cultured meat and the reality of its commercial progress. Despite years of investment and development, lab-grown meat has struggled to reach mainstream consumers at scale. The article questions what went wrong with a technology that was once heralded as a sustainable solution to industrial animal farming.

0
ProgrammingDEV Community ·

Why Uptime Metrics Fall Short as Reliability Benchmarks for AI Agents

Traditional uptime and HTTP success rates are insufficient measures of reliability for AI agent systems, as an agent can return a healthy status code while failing to complete tasks correctly or safely. Experts recommend splitting agent reliability into distinct indicator families covering task success, safety controls, latency, efficiency, and escalation behavior. Safety-related metrics, such as the rate of authorized versus unauthorized actions, must never be averaged into general availability scores, since a single policy violation can be masked by otherwise healthy aggregate numbers. Business outcomes, like whether a notification was delivered or acted upon, should be tracked separately from runtime completion using a shared decision ID to enable later reconciliation. SLO targets for agents should be grounded in product risk, user expectations, and observed baselines rather than copied from unrelated systems.

← NewerPage 977 of 3189Older →