Writing

Software rewards close attention — the more precisely you understand what a system is doing, and why, the better the decisions you make on top of it. Writing is how I develop that precision: it forces the gaps in understanding into the open, where they can be examined and closed.

What follows is a record of that process. Posts on systems, low-level programming, Unix, and the design decisions that recur across everything I build. Much of it lives in the territory of systems programming and low-level C — which is where my attention is currently directed.