Before adding a database table to a working feature, it's worth asking what actually changes — not just in the code, but in what you're now responsible for. A planning walkthrough for turning a stateless AI-triage feature into a persistent, queryable one, and the retention and privacy questions that come before the first line of SQL.
*What started as a simple "hello world" exercise turned into a deep dive into how Zig and Roc actually build binaries — from optimization modes and DWARF debug symbols eating 94% of a binary's size, to a surprising 14x size gap between a tiny Zig executable and its Roc equivalent. Here's everything I learned, one command at a time.*
A video on Julia's @generated functions turned into a REPL session proving every claim by hand
The real payoff came last: the official HTTP API silently hung with no error, so reading the node's own source code on GitHub uncovered its raw socket protocol instead — and a hand-built Python client, no SDK, no libraries beyond socket and json, ended up pulling live chain data straight off the wire.
A broken npm symlink, a 400 from Claude extra usage, and a home directory full of every project on the machine. Then one repo, four tools, three commits.
What I set up I already had Zed, Roc, and Zig on my Debian machine from earlier. Tonight I treated learning like a work block: show up, practice, stop when tired. I made a home base: Bash I open that…
Setting up a real Security Information and Event Management (SIEM) system in a home lab has been on my list for a while. I wanted something powerful enough to teach me real cybersecurity skills, but free and self-hosted. After comparing…
Today was spent setting up two complete learning environments and practicing the fundamentals of both Python (scientific computing) and Rust. Python / SciPy Environment Rust Environment Both environments are now clean, isolated, and ready for continued learning — one focused…