import chaos

A breaker closing can return full traffic to a dependency that is still fragile.

Building slap5, a five-in-a-row engine in Rust and WebAssembly, and finding out how much work lies between working code and a strong opponent.

The Database Safari, a practical field guide to specialized databases and hybrid data architectures, is now available.

Twenty-one correctness scenarios run against eleven pinned fetch resilience libraries: 122 cells pass, 25 fail, and 84 combinations no library offers.

A deliberately simple watermark model shows how much room a text watermark has: the entropy available at each token, how a small bias becomes detectable, and why length matters.

Combining distributed resilience policies changes what each one counts and protects.

A rate limit is one timestamp in one process and a distributed-systems problem once that timestamp is shared.

What a rate limit constrains, how token bucket and GCRA represent rate and burst, and how their bookkeeping affects admission decisions and retry hints.

A concurrency limit is easy inside one process and a distributed-systems problem once it is shared.

The circuit breaker pattern is simple in one process and much harder across a fleet.

The fetch promise resolves when the headers have been parsed, while the body is still arriving over an open socket.

chaos-sw brings browser-wide network chaos injection to every controlled tab, and chaos-fetch 1.3.0 adds origin-aware route matching and cleaner public config types.

ffetch had a full suite of passing tests for retries, hedging, timeouts, and cancellation.

JavaScript's typeof operator is useful, but it is not a real type system.

Four fetch-kit releases with new fuzz tests, bug fixes, hardened CI and release pipelines, and OpenSSF Scorecards.

JavaScript's structured clone algorithm preserves cycles, shared references, and many built-in types, but it still rejects or transforms values when data crosses a boundary.

Mathematical formula rendering is now supported on this blog, powered by MathJax.

ESM and CommonJS expose values through different contracts.

How statistical text watermarks encode machine-readable signals in ordinary prose, how detectors recover them, and how copying, editing, and rewriting affect the result.

A reliable text-watermark detector can find an engineered statistical signal, but that result alone cannot reconstruct authorship, intent, or policy compliance.

Object storage is separate from application state: how partial uploads, stale URLs, key collisions, CDN caches, and deletion create inconsistencies, and how to design for cleanup and recovery.

JSON looks like a faithful representation of JavaScript data, but JSON.stringify and JSON.parse can silently alter or discard information at system boundaries.

Databases are where correctness becomes shared state: how invariants break under concurrency, when transactions help and when they don't, why reads go stale, and how to design for retries, migrations, and recovery.

How a layoff and a security clearance wait turned into a year of open source projects, technical writing, and discovering what happens when work and side projects align.

Go 1.24 replaces the old bucket-and-overflow map internals with a Swiss Table-inspired design to improve cache locality, lookup speed, and memory efficiency.

The built-in Date API is full of traps: unreliable parsing, mutation, timezone confusion, and broken arithmetic.

Both chaos proxies gain structured --verbose observability, and every fetch-kit repo moves its release automation to a GitHub App with fixed Discord announcements.

Time is where application code meets uncertainty: clock skew, wall-clock corrections, ambiguous ordering, late schedulers, and business-calendar boundaries.

The network is where application code meets uncertainty: latency, retries, timeouts, duplicate side effects, degraded states, and ambiguous outcomes.

console.log() feels like a direct window into your program's state.

I launched a newsletter for import chaos with new posts, practical engineering notes, and occasional release updates.

The fetch-kit ecosystem finally has a dedicated website at fetchkit.org, with overviews of all tools, examples, and the chaos arena.

npm, Yarn, pnpm, Bun, and Deno are not interchangeable install tools.

Stars and downloads tell you about popularity, not safety.

Building a Go-based CLI tool to export Confluence spaces to local Markdown files for RAG pipelines, offline docs, and Git-based knowledge management.

Tail-recursive code in JavaScript still risks stack overflow in real-world runtimes.

A deep dive into the Go compiler pipeline: from lexing and parsing to SSA, optimization passes, and code generation.

You tightened your client with retries and resilience knobs.

How to add convenience methods to a native Promise object without subclassing, wrapping, or changing what await returns.

A production-ready TypeScript-first drop-in replacement for native fetch.

ffetch-demo is a live browser arena for benchmarking JavaScript HTTP clients under controlled network chaos.

Throttling reduces noisy UI events, but naive implementations can drop the final state.

Unify response caching and in-flight request deduplication with Cloudflare Durable Objects to eliminate duplicate work during cache misses in distributed systems.

Debounce smooths UI events but does not fix request lifecycle bugs.

Compare the performance of chaos-proxy in Node.js vs Go for HTTP chaos testing.

A production-ready TypeScript-first drop-in replacement for native fetch.

How to find the top-K items in Go using heap and streaming approaches.

Exploring the growing ecosystem of modern databases and the journey from the Database Zoo series to the upcoming book, The Database Safari.

Exploring how pagination strategies can impact GraphQL performance in Node.js applications.

Running a privacy-first disposable email service: Lessons from handling domain abuse flags, ServerHold suspension, and registry issues with nullmail.cc.