I just miss doing art. Don't you?

When most people think “river” I bet they think “personal identity.”

Writing custom Rust lints for fun and profit

what's a few systemd services in initramfs between friends?

use pre-push hooks instead

programming isn't a competition

Some definitions and an overview of the world of build systems

I want a way to gradually transition existing builds to be hermetic.

Makefiles and Ninja files have limitations, separate from the implementing tool. How can we fix them?

A build system needs to know not just which files exist, but which shouldn't exist.

You have backups for your critical data. Do you have backups for your critical infrastructure?

To redesign infrastructure, you have to allow incremental adoption, while simultaneously moving the whole design space at once.

an overview of what builds for complicated projects have to think about

within Rust is a smaller language struggling to get out

say what you mean to say, not just the first thing on your mind

hiring in tech is broken and everyone knows it. what can we do better?

your data is trapped inside the box that is your program. you can only see what the program author exposes.

exposing raw pointers make the optimizer’s job horribly hard. high level languages can constrain your program, making more optimizations sound.

a couple days ago i pushed about 10 empty posts at once to everyone subscribed to my RSS feed. oops. sorry about that.

i've since fixed it, but most RSS readers i've seen will cache the posts indefinitely once they're published. the workaround for my own client was to delete my page and then readd it, which will unfortunately discard all your read/unread state.

the reason this happened is that i added a new kind of "stub" post, and handled that correctly on the main site, but not on the rss feed. you can see the intended layout of the stub posts here if you're interested.

writing programs should be no harder than writing a resume

how hard is it to save and restore program state?

the trick is to make it as easy as possible

i have gone a little above and beyond trying to get all the features of VSCode

learning how a program is intended to work is hard. here's how to do it.

"technical debt" is about updating your understanding of the program over time. "technical risk" is about sacrificing your ability to make changes for speed of development in the short term.

unix sure is a system

tools i use or want to use

new and exciting ways to write buggy code