SShortSingh.
Back to feed

Four Engineering Rules That Keep AI Systems Running When They Fail

0
·3 views

Software engineer Derek Wang argues that AI systems fail differently from humans — silently and without warning — making resilient implementation a critical design layer for AI-coding projects. Wang identifies four core principles: idempotency (ensuring repeated operations produce the same result), graceful degradation (keeping core functions alive at reduced quality during partial failures), visibility (alerting users or monitors when fallbacks activate), and fast recovery. Drawing from his own trading system, he illustrates how database upserts prevent duplicate data on retries and how cached exchange-rate fallbacks keep quote functions running even when external feeds go down. He warns that silent degradation is more dangerous than an outright error, since downstream systems may act on stale or incorrect data without anyone knowing. A real incident in which all workers in his multi-agent system crashed simultaneously — traced to shell scripting misuse — underscores his broader point that background AI processes require explicit error handling rather than strict fail-fast defaults.

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 ·

Developers Can Build Zero-Cost Semantic Search Without LLMs Using FastAPI and Qdrant

A technical guide published on DEV Community outlines how to build a production-grade semantic search engine without relying on large language models or paid AI APIs. The proposed architecture uses FastAPI, Qdrant in-memory vector storage, and Hugging Face's free serverless inference API to generate 384-dimensional text embeddings. Unlike keyword-based search, the semantic approach converts queries into vectors, allowing it to match conceptually similar content even when exact words differ. The entire stack runs on a serverless, Jamstack infrastructure hosted on GitHub Pages, designed to cost nothing at scale and return results in single-digit milliseconds. The guide argues that for the majority of real-world search use cases, direct context-aware document retrieval is more practical and efficient than generative AI responses.

0
ProgrammingDEV Community ·

Developer Builds Android App to Edit, Transfer, and Manage Files Without a PC

A developer frustrated by the repetitive cycle of moving files between phone and PC built an Android app called HandyPC to handle the entire workflow on a single device. The app combines a file explorer, text editor with search and replace, SCP/SSH terminal, and basic network diagnostics tools in one place. It supports features like zip file handling, encoding detection, dual-pane view, and wired Ethernet connections via USB-C adapters. The goal was to let users complete the full find-open-edit-send workflow without switching apps or devices. HandyPC is available on the Google Play Store with a free two-month trial followed by a one-time purchase.

0
ProgrammingDEV Community ·

DEV API analysis of 1,634 posts finds no dominant off-site publishing platform among writers

A writer analyzing DEV Community's public API sampled 1,634 recent articles during a roughly four-hour window on September 23, 2026, to identify where authors publish beyond DEV itself. Of those articles, 81.8% declared DEV as their canonical home, while the remaining 18.2% pointed to 149 distinct external hosts. Among those 149 external destinations, 148 were used by exactly one author each, with Medium being the sole exception, hosting just three posts from three different writers. The analysis accounted for platform subdomains using Mozilla's Public Suffix List to avoid inflating destination counts from services like Blogger or GitHub Pages. The core finding is that DEV writers who publish elsewhere do so on their own personal domains, with no single shared platform serving as a meaningful secondary hub.

0
ProgrammingDEV Community ·

Go Basics: When to Use 'go run' vs 'go build' in Your Projects

Go is a compiled language, requiring source code to be translated into machine code before execution. The 'go run' command compiles and immediately executes code via a temporary file, making it ideal for quick testing during active development. In contrast, 'go build' produces a permanent standalone binary that can be deployed to servers or shared with users without requiring Go to be installed. Go also supports cross-compilation, allowing developers to build binaries for Windows, Linux, or macOS by setting the GOOS and GOARCH environment variables. Choosing the right command depends on the stage of development — 'go run' for iteration and 'go build' for production-ready deployment.