Ai-Slop

Every developer has a ~/dev/tools/scripts folder. Mine has run for years without an index. I asked Claude Code to read every file in it and write one. The brief was simple: read the whole directory, then produce an INDEX.md with three columns — tool, how to run it, what it does. It scanned roughly 40 files: Python CLIs built on uv, shell wrappers, one-off Snowflake key-rotation scripts, a tmux session launcher, a Hacker News summarizer. Some had docstrings. Several had none, and their purpose was recoverable only by reading the argparse block or the hardcoded constants at the top. ...

Most developers have a graveyard of dotfiles, .env files, and Slack DMs containing tokens that were supposed to be temporary. This post describes the pattern I use to keep all local dev secrets in a password manager and inject them into my shell on demand — nothing sensitive ever touches disk. The full setup lives in my dot-local repo on GitHub, including the helper functions and new-machine setup guide. The Problem I work across multiple machines: a work Mac that uses 1Password and a personal Mac that uses Bitwarden. I needed a single pattern that worked on both without maintaining two separate codebases or hardcoding tool-specific logic everywhere. ...

This one’s ai-slop, as advertised on the about page — built with Claude Code over a couple of months of on-and-off sessions. Most people who read a lot online never see any of it again. Someone opens an article, skims it, closes the tab, and forgets it — buried inside browser history nobody searches. Archivore, a small command-line tool, exists to fix that one habit at a time. The idea is simple: capture everything worth keeping, automatically. Archivore scans browser history since its last run, picks out links from Hacker News, Reddit, and X, downloads the linked article, and converts it to Markdown. Nothing requires manual saving or tagging. Opening a link in a browser is enough. ...

This one’s ai-slop, as advertised on the about page — I paired with Claude Code to build this site’s entire publishing pipeline, and it seemed only right to have it write up its own plumbing. Here’s what’s actually running under the hood. Hugo, with PaperMod The site is a static Hugo build using the PaperMod theme, installed as a proper git submodule (not vendored — git submodule update --remote themes/PaperMod pulls upstream changes when I want them). Two sections get custom layouts instead of PaperMod’s defaults: ...