SShortSingh.
Back to feed

The 'Blast Radius' Rule: How to Decide What AI Coding Agents Should Handle Alone

0
·1 views

A developer writing for DEV Community outlines a practical framework for delegating tasks to AI coding agents based on how reversible their failures are. The core idea divides work into zones: fully reversible changes like UI and copy are safe for agents to handle independently, while silent failure-prone configs like cache headers and robots.txt require human verification. A third zone covers irreversible actions — DNS records, app store listings, secrets, and anything referencing live external URLs — which the author never delegates regardless of the agent's competence. The author learned this after an AI-generated Cloudflare cache rule produced a malformed HTTP response that looked correct in the diff but was only caught by manually inspecting live traffic. The proposed fix is to encode these constraints directly in the repository, using comments and build-time checks so both future humans and AI agents inherit the context automatically.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

29,000 Home Weather Stations and AI Agents Tested as Volcanic Early Warning System

Researchers used over 29,000 consumer-grade Netatmo barometric sensors across Japan, combined with Google Apps Script cloud archiving and Gemini AI agents in the Antigravity CLI environment, to detect atmospheric shockwaves from volcanic eruptions. The system was validated against two historical Japanese eruptions — the 2018 blasts at Mt. Kusatsu-Shirane and Mt. Shinmoedake. It reconstructed shockwave velocities within 98.5% of theoretical sound speeds, pinpointed unmonitored crater directions to within 1.78 degrees, and estimated explosive yields ranging from roughly 179 to 1,041 tons of TNT equivalent. The crowdsourced sensor network delivered between 2.5 and 15 minutes of advance warning with no recorded false positives, even during violent storm conditions. The findings, published on ESS Open Archive, suggest that dense consumer IoT networks grounded in physics-based AI analysis could help fill the large blind zones left by sparse government monitoring infrastructure.

0
ProgrammingDEV Community ·

Japanese TTS Bug Turned 'Shōshō' Into Gibberish Due to Unicode Whitelist Gap

A developer discovered that a text-to-speech system for a virtual inquiry desk was garbling Japanese phrases, turning '少々お待ちください' into something that sounded like 'shomo o-machi kudasai'. After ruling out the voice model, cache, and synthesis parameters, the root cause was traced to a preprocessing function that stripped characters not on an allowed list. The character '々', a common Japanese iteration mark, was excluded because Unicode classifies it under 'CJK Symbols and Punctuation' rather than 'CJK Unified Ideographs', which the whitelist covered. Further review revealed several other affected characters, including range symbols, colons used in time expressions, and rare kanji variants used in proper names. The fix required not just expanding the allowlist but converting ambiguous symbols like '〜' and ':' into Japanese-readable equivalents before synthesis.

0
ProgrammingDEV Community ·

DeepSeek Harness: Open-Source Agent Runtime Offers Full Transparency and Plugin Control

DeepSeek Harness (dsh) is an open-source, MIT-licensed code agent framework built on Cordis, a plugin-based runtime where every component — tools, UI, sandboxing, and orchestration — is a replaceable plugin. Unlike closed tools such as Claude Code, it provides a Trajectory view that logs each agent turn with precise timing, token usage, and full tool input/output, allowing developers to pinpoint exactly where a run failed. The framework enforces granular sandbox policies at the kernel level using Seatbelt and Landlock, with three access modes ranging from read-only to full-access, and sensitive operations require explicit human approval. Structured, readable error messages replace cryptic stderr output, making permission denials actionable rather than opaque. The project can be launched via a simple CLI in web, headless, or custom-profile modes, positioning itself as a distinct category of agent tooling aimed at transparency and developer control.

0
ProgrammingDEV Community ·

GEO Optimisation Builds on SEO Foundations, Not a Replacement for Them

Generative engine optimization (GEO), coined in a 2023 academic paper by Aggarwal et al., demonstrated visibility improvements of up to 40% within AI-generated answers using a structured benchmark called GEO-bench. However, the research also found that effective techniques vary significantly by domain, meaning no single universal GEO playbook applies across all content types. Google has confirmed that its AI Overviews and AI Mode draw from the same index and quality systems as classic Search, with no separate submission process for AI visibility. Core technical fundamentals — fast pages, clean semantic HTML, schema markup, and proper heading structure — remain essential for both traditional crawlers and AI retrieval systems alike. Experts note that most citation failures stem from technical issues such as JavaScript rendering problems or misconfigured bot rules, not content shortcomings, making a strong SEO foundation a prerequisite for any GEO effort.

The 'Blast Radius' Rule: How to Decide What AI Coding Agents Should Handle Alone · ShortSingh