Authors
AUTHORS
C2CZ is written by five engineers, each responsible for one beat. Every article is verified before publication: the failing case is reproduced, the fix is executed, and the version it was tested against is recorded in the article. When something is corrected, the correction is published on the page rather than quietly edited away.
The standards behind that process are in our Editorial Policy.
Who writes here
Alex Rivera · Cloudflare Workers and the serverless edge · 15 articles
Alex Rivera writes the edge and serverless half of C2CZ. The beat is Cloudflare Workers: runtime errors that only appear once code is live, module resolution and compatibility-date problems, stream and body handling, the limits of the global scope, and the crypto APIs Workers expose.
Elif Demir · databases and container networking · 7 articles
Elif Demir covers data layers and how containers reach each other: SQLite locking under concurrency, D1 statement and variable limits, Docker and WSL2 network modes, and the connection errors those two worlds produce.
Kai Tanaka · SSH, TLS and applied cryptography · 10 articles
Kai Tanaka handles keys and certificates: SSH host and agent errors, mTLS handshake failures, certificate chain validation, and the OpenSSL 3 rejections that break configurations written for older versions.
Mara Voss · Docker, system limits and reverse proxies · 12 articles
Mara Voss covers the systems layer: Docker daemon failures, Linux resource limits and file descriptors, exec and shebang problems, OpenSSL provider changes, and the proxy errors (499, socket hangs, unexpected EOF) that appear between a client and an origin.
Noah Lindqvist · hardware, processes and Unix internals · 12 articles
Noah Lindqvist writes about the machine underneath: 3D printer firmware faults (Klipper), SD card and USB descriptor errors on single-board computers, zombie and orphaned processes, file descriptor exhaustion, and the argv and environment limits of execve.
How an article gets published
Each piece is drafted against the real error, the reproduction is run, and the result is checked before it goes live. Articles carry the date they were last verified so a reader can tell whether an instruction has been re-tested since it was written. Corrections are logged on the page.