Write after the system has argued back.
I am not interested in turning release notes into thought leadership. These are accounts of what changed once a tool met its real workload, plus conversations about the systems underneath.
Long-form notes.
Designed to be read here: generous measure, quiet typography, useful code, and nothing fighting the argument.
How AI workloads changed the queue I was already building
Why streaming, budget enforcement, token-aware limits, and pause/resume moved into glide-mq instead of remaining a second system around it.
Your AI agent configs are probably broken (and you don't know it)
Agent configuration fails silently across skills, hooks, memory, MCP, and tool-specific formats. The case for treating this layer like code.
Talks and conversations.
The same systems, with room for the questions that do not fit cleanly into an article.
Inside Valkey GLIDE
Rust at the core of a multi-language client, zero-config ergonomics, socket security, and community feedback.
Let's Talk About Data · videoGlide into resiliency
Practical Valkey GLIDE patterns, client reliability, Pub/Sub, vector data, sessions, and real integration examples.
Stack Overflow · 70 answersSmall, specific answers
Redis and Valkey, Node.js, AWS, GitHub Actions, TypeScript, and the bugs that only appear in somebody else's setup.
DEV Community · canonical cross-postsMeet readers where they already are
The original community editions of the essays, including comments and discussion.