Essays with 5+ minutes reading time that reward close reading.
TypeSafe AI's Jev does not want to write your email, explain quantum mechanics or generate an application. It wants to answer a smaller question quickly: given this state, which bounded decision should software make next?
Why Rust won AI infrastructure: its ownership model, zero-cost abstractions, and precise memory layout control eliminate GC pauses and wasted bandwidth - exactly what matters when cost per token is a memory problem, not a compute one
A practical loop for keeping AI agent evals fresh: capture production traces with outcome labels, curate the failures worth testing, convert them into property-based eval cases, and verify fixes against both evals and production failure rates.
Retrieve-for-Train suggests a practical design shift: learn repeatable search behavior offline, but keep live facts and permissions online.
Persistent memory is becoming an infrastructure feature. The harder problem is deciding what an agent may remember, trust, update, and forget.
An LLM demo can be built in an afternoon. A system that uses an LLM safely, economically and repeatedly under production traffic is a different discipline.
Stop over-provisioning cloud block storage on guesswork: watch queue depth, p99 latency, and burst balance to tell whether you're IOPS-, throughput-, or capacity-bound, then scale only the knob that's actually throttling with the cost math to prove it.
A practical framework for deciding when off-the-shelf models have reached their limit—and when your data, economics, and constraints justify building your own.