What the gate checks: lend's approvals, Starlette's Host header, FastAPI's Depends object
Four items from this week turn on the same detail: a control that looks complete holds only for the exact thing it inspects.
Software news, read and annotated by a working engineer
Four items from this week turn on the same detail: a control that looks complete holds only for the exact thing it inspects.
Three posts from 14 and 15 November use AI models for very different jobs, and each describes a separate step that decided whether the output could be trusted.
Three items from 12 to 14 November turn on a default value, and each shows a different way to change one without breaking the people who relied on the old behaviour.
Three notices from 10 to 13 November replace case-by-case judgement with a rule that can be checked by a machine, and each one moves work to the people downstream.
Three notices from 11 and 12 November share one lesson: the support window, not the version number, decides how much work an upgrade will be.
A critical race in httpd's mod_http2 and a cluster of high-rated HTTP/2 and TLS fixes in Node.js landed the same day; both point at the state a server keeps per stream.
Three items from 10 November show security depending on a party the user rarely looks at: an inference vendor's retention promise, an app's private Git, and an alert that stops on its own.
Three announcements from 9 and 10 November place safety checks in the inference layer, the hypervisor and the finished build log rather than in code that teams write and change.
An Oracle benchmark, a Google wearable study and a LangChain4j reviewer each drew a line around their own result.
The Forwarded header passes through proxies that never set it, and musl's crypt() error value equals the field of every passwordless account.