k4i.com now publishes three kinds of post on its own: risk factor changes from 10-K filings, earnings guidance checked against results, and a chip and AI infrastructure press release digest. No server, no paid inference, no one at the keyboard. Each one is a scheduled GitHub Actions workflow in the site’s repo that reads a public source, runs it through a model, checks the output with plain code and commits a Markdown file. Cloudflare Pages builds the site from there.

Asynchronous code has a reputation for being confusing, but the core idea is simple: stop waiting. This post starts from zero — no prior async experience assumed — and builds up to the parts people usually find murky: how the event queue, the event loop, and the thread pool connect, and what coroutines, await, futures, tasks, gather, queues, cancellation, and starvation actually mean. Every concept comes with a small, runnable example.