Rust async stream processing: walking a 4 GB event log without blocking the runtime
The Log
Mon, Oct 26
We ingest a rolling 4 GB event log across hundreds of thousands of lines, and the first cut blocked a worker on every 8 MB page fetch. Here is the async stream version that keeps the runtime hot end to end — patch, review comments and all.
62 like
19 love
28 insight
Delete this post? You can undo for 30 seconds.
Hot take: most design systems are just component libraries with a marketing page
Hot take: most "design systems" are just component libraries with a marketing page. The actual system is the decisions — spacing scale, type ramp, motion language — not the button variants. (Yes, I will die on this hill.)
41 like
12 love
9 insight
Delete this post? You can undo for 30 seconds.
Thu, Oct 22
The tools I trust are the boring ones — what quietly carries your workflow?
The tools I trust are the boring ones: ripgrep, fd, make, jq. Every shiny dashboard eventually becomes a shell alias. What "boring" tool quietly carries your whole workflow?
30 like
8 love
14 insight
Delete this post? You can undo for 30 seconds.
That's the root post. There's nothing before it.