scuffed wiki

I’m a programmer living in the PNW. I have a background in backend engineering and infrastructure management. I don’t consider myself an artist, but I love to dabble in the creatives (music, drawing/painting, building). You can find my work scattered all over this wiki-like-abomination. I’m a decades-long linux user and I try my best to stay within that ecosystem as much as I can. Sometimes I have to break out into windows or macos to work with tools that are next to impossible to get working correctly in wine or proton. My year of the linux desktop was like 1999 or something.

When computers annoy me, which is often, I’m usually gardening, working on the house, climbing or hanging out with all the people I care about.

This is a static site that’s generated from markdown files. The generator was written in Go. It contains a few top-level sections, found up there in the navigation bar. These are not static entries; the generator walks the contents directory and builds the entire site structure, forming indexes from child directories (and index.md files) and building pages from other content files (markdown, html, txt). The generator builds a dynamic lexicon based on the file and the frontmatter entries. This lexicon contains terms that point to pages. These pages are then linked to by the generator when it scans the contents of each page and finds uses of existing terms.

Here I will write pages in a couple different formats:

• log: this is a chronological blog-style series of posts.
• notes: quick-ish notes about stuff and things.
• projects: these are pages and indexes about the various things I build; this includes code projects, electronics, yard/garden, wood working, and other tactile shit.

what is e64ec?

It’s the only commit that matters. A guaranteed way out of a sticky situation.