Most of this started because I wanted to know how something actually works, down to the layer nobody looks at.
Every repo says how it was measured and where it loses. I've been burned enough times by my own benchmarks to be careful about that.
falcondb · Rust
A columnar analytical database, written from the storage format up. Faster than DuckDB and DataFusion on all 26 points I measured, and slower than everyone at loading Parquet.
netwatch · Rust
Which program is using your connection, live. Reads the kernel's own accounting instead of polling, so a process that lives two seconds isn't missed.
falconnet · Rust
SQL over packet captures. Wireshark shows you frames; this answers questions.
synchronize · Go
Keeps my git repos in step across machines. Written after losing an evening's work to the laptop I wasn't sitting at.
help-finder · Python
Finds questions nobody has answered yet, across seven sites.
Each answers one question and stops.
- sql-traps — the same SQL on four databases, where the answers differ. More often than you'd like.
- workflow-doctor — where a GitHub Actions run loses its minutes.
- flakemap-contrib — catches a flaky test in the PR that added it.
- jest-polluter-finder — which Jest file breaks the test you're staring at.
- dockerfile-diff-size — which instruction made the image bigger.
- vk-chain — how you know someone on VK, in hops.
- mini-player — floating video windows that stay on top.
- desktop-focus — hides every icon except the ones you want.
Some of the forks here are patches to projects I use, not abandoned copies — sotto among them.
If something doesn't build on your machine, open an issue. I'd rather know.