Some devices are like bad relationships, offering brief moments of hope before crushing disappointment. The office printer is one such device.

I didn’t build Cookslate because I wanted a side project. I built it because every recipe app I tried treated cooking like a Pinterest mood board instead of something you actually do with your hands.

I’ve been using Trilium Notes for years to manage everything from homelab documentation to music catalogs, and every time I mention it at work, I get the same blank stare. That’s not Trilium’s problem.

Everyone wants to talk about the flashy gear. Nobody wants to talk about the box sitting quietly in the corner that makes all of it matter. That’s the NAS, and it deserves a harder look than it gets.

A hobbyist reflects on maintaining an extensively over-engineered home server setup that far exceeds the demands of its nominal purpose, arguing that framing the project as infrastructure for something else…

I’ve got two servers in my homelab that are supposed to be different environments. Lately they’ve been lying to each other. And honestly, I’m the one who let it happen.

There are two kinds of homelab builders: the ones who label everything and the ones who will spend forty-five minutes at 11pm tracing a mystery ethernet run with a flashlight. Both approaches have something real to say about how people actually think about permanence.

I just wanted to stop losing recipes to dead browser tabs and sticky notes. What I got instead was a crash course in every layer of web development I had been successfully avoiding for years.

Most people have a storage strategy, not a backup strategy. There’s a difference, and you will learn it at the worst possible time.

Most people treat NAS like a glorified external hard drive. I’m here to tell you that’s exactly where they go wrong, and I’ve got four of them to prove it.