case studies
An access logger writes one JSON line per request. In Go, the usual way to make that cheap is to append into a buffer the caller owns: no fmt, no encoding/json, no …
case studies
A log pipeline pulls query parameters out of request paths, millions of times a day. The function that does it is eight lines of hand-written splitting. It’s fast, …
case studies
Some tools are judged by their size. A small binary that gets copied onto every build agent, baked into container images, or downloaded at the start of each CI job pays …
releases
The first jvq release read one thing: the output of Go’s go test -bench. That covered Go projects and nothing else. Version 0.2 drops the limit. If your benchmark …
releases
Until now jvq came with a GitHub Action and a line in the README saying GitLab works the same way. It did, if you worked out the base commit, the clone depth and the …
releases
Version 0.2 let jvq gate a benchmark in any language, by timing the whole command or reading a few lines of JSON. That still meant a little glue for projects that already …
case studies
Most log files older than a day are compressed. Logrotate gzips them, object storage keeps them as .gz, and the habit for querying them is a pipe: zcat app-*.jsonl.gz | …
releases
Application logs tend to end up in the same shape: a file of a few gigabytes with one JSON event per line, and a question about it. How many 500s per service since the …
releases
Most slowdowns get in one pull request at a time. An extra allocation in a loop, a string copied where a slice would do, a log call on the hot path. Each costs a few …
testing
A gate that blocks merges has two ways to fail. It can cry wolf, flagging changes that did nothing, until people stop trusting it. Or it can sleep through a real …