We want to hook a function, so that our code gets called... but we also want the original code to execute. How the heck does that work?

As of today, I am no longer employed by fly.io.

We're both very sad, and we've promised to stay friends and send postcards to each other over winter break. (I'm excited, too — Annie makes great postcards)

HTTP does a pretty good job staying out of everyone's way.

If you're reading this article, there's a solid chance it was delivered to you over HTTP. Even if you're reading this from an RSS reader or something. And you didn't even have to think about it!

I don't mean to complain. Doing software engineering for a living is a situation of extreme privilege. But there's something to be said about how alienating it can be at times.

In 2020, I switched from a static site generator to something homemade.

And, as tradition commands, I did a whole write-up about it.

In this series, I change a critical component of this website's asset pipeline from "just calling a bunch of external tools" to statically linking with everything I need to process assets. It involves autoconf, CMake, Meson, CI, pkg-config, and some code crimes.