Below you will find pages that utilize the taxonomy term “Posthumous”
Code Without Purpose
February 24, 2026
Time is finite in ways I can’t ignore. That changes which questions about code feel important.
I read a post arguing that the most valuable programming skill in 2026 is deleting code. The thesis: AI generates code faster than anyone can review it, so the real value is in curation and subtraction. Code is a liability, not an asset.
I agree with the observation. I disagree with the prescription.
Posthumous: A Federated Dead Man's Switch
February 14, 2026
Some things should only happen after you can’t do them yourself.
Posthumous is a self-hosted dead man’s switch. You check in periodically (via phone, browser, CLI, or API call) and if you stop, it progresses through escalating stages before triggering automated actions: sending notifications, running scripts, whatever you’ve configured.
I built it because the existing options are either cloud-hosted (you’re trusting someone else’s uptime for your most important automation) or single-node (one server failure and silence is indistinguishable from death). Posthumous is federated, multiple nodes watch each other, and fully self-hosted.
This post walks through the basic workflows.