Posts

For context on how my brain works, see Working with an AuDHD Brain. This is the stack that structures my daily work: taskwarrior for task management, timewarrior for time tracking, and vit as a vim-style interface. Together they form a keyboard-first, terminal-native productivity system. No Electron apps. No cloud sync sending your data to Silicon Valley. Just plain text, local, and blazing fast. Why This Stack? I struggled with task management for years. Todoist, Things, Notion, Obsidian plugins — tried them all, eventually abandoned them all. The problem was always the same: too much friction. ...

I self-host nearly everything. Kubernetes clusters on refurbished mini-PCs. GitLab on my own hardware. Vault for secrets. Monitoring, logging, all of it. People often ask: why? Managed cloud is easier. AWS, Azure, Google do it at scale and reliably. Why put yourself through this? The short answer: agency. The long answer is this entire article. The spaceship thought experiment In my post about the space container thought experiment I describe a scenario: you wake up in a closed container in space. Everything you need to survive is present, but nothing goes in or out. ...

I have AuDHD — the combination of autism and ADHD. Specifically ADHD-PI: the inattentive variant, without the hyperactivity most people associate with ADHD. This isn’t an excuse. It’s context. Because the way I work — the obsession with automation, the preference for async communication, the hours I invest in tooling — doesn’t come out of nowhere. It’s the result of years of experimenting with what works for a brain that isn’t built for the standard office world. ...

As a kid I had a word for things that fascinated me: unbreakable. Not “indestructible” — that implies something never breaks. Unbreakable is different. It means something even broken still works. I remember exactly when that fascination began. A photo of an A-10 Thunderbolt II, returned from a mission. Half the wing gone. Tail in tatters. Fuselage full of holes. And yet that thing had brought its pilot home. That’s not luck. That’s design. ...

GitOps changed how I think about deployments. Instead of running commands against a cluster, I push to Git and watch the cluster converge to the desired state. It sounds simple, but the implications are profound. ArgoCD is my tool of choice for GitOps. Let me show you why, and how to get started. Why GitOps? The Philosophy First Before diving into ArgoCD, let’s understand why GitOps matters. Traditional deployment: Developer → kubectl apply → Cluster The problem: What is deployed? You have to query the cluster. Configuration drift happens silently. Rollbacks are manual and error-prone. There’s no audit trail beyond “someone ran kubectl.” ...