hoelz.ro

A while ago, my friend and coworker Matt pinged me with a Git question.

When writing PromQL, I very rarely run into nan, but when I do, it can be kind of a pain to deal with, since it: Read More...

One great thing about SQLite is that it's a super-widely-used format, so you can fire up sqlite3 to poke around your applications' data, or use your favored programming language's SQLite library.

Like many users of Prometheus, at work we use labels with AlertManager's routing to make sure the right people get paged when something goes wrong.

The fact that tj-actions/changed-files was compromised is kind of old news at this point, but I had an insight the other day about this problem and its remediation that I haven't seen mentioned yet.

I was working on a PromQL query at work to find disk usage on Kubernetes control plane nodes - the first step was to identify those nodes: Read More...

I use restic to manage backups on my machines, and not too long ago I ran into some surprising behavior that I thought I'd share.

I've been working through Mastering Distributed Tracing to learn more about (you guessed it) tracing.

At work, we have a Prometheus metric from our build system named autobuild_build_timestamp that exports the timestamp for the latest build for a given application and Git branch.

I recently ran into a surprising behavior when calling a Lambda function from the command line that I thought I'd share.

Recently, I wanted to find a document in my personal wiki that mentioned the idea of "there will always be another coding task" - unfortunately, traditional search came up short here, because I couldn't remember the exact wording I used, only the "vibe" of

The trick I covered in my previous post got me reflecting on "clever" code.

While digging in and doing research for my previous post, I came across a really cool trick that glibc uses to provide a single macro for invoking system calls, no matter how many arguments they take.

A few months ago I was using bpftrace to implement a program to monitor writes to a specific directory, and while working on this program I encountered some noteworthy behavior around bpftrace and its filters that I thought I should share.

For this post, I wanted to talk about a trick I came up a few years ago with to apply Git's pickaxe option in a situation where the change I was interested in wasn't contained in a single line.