Documentation Is the Cheapest Network Upgrade You’ll Ever Buy
Good documentation doesn’t make a network faster. It makes problems smaller. Here’s what actually matters and how to build the habit before you need it.
Read moreWriting
Networking, infrastructure, web development, iOS, and whatever else seems worth putting down in writing.
Good documentation doesn’t make a network faster. It makes problems smaller. Here’s what actually matters and how to build the habit before you need it.
Read moreWhen one machine quietly becomes responsible for everything, maintenance becomes impossible and every change feels risky. Here’s what to watch for before it happens.
Read moreA successful backup job and a successful recovery are two different things. The restore test is the only one that actually matters.
Read moreAdding virtualisation didn’t make things more complicated. Snapshots, isolation, and portability reduced the effort required to keep everything running.
Read moreA firewall handles the perimeter. The real security problems are usually inside it. Here’s what a thoughtful security approach actually looks like.
Read moreMost hardware failures trace back to the environment before they trace back to the equipment. What’s around the rack matters as much as what’s in it.
Read moreAfter years of maintaining nginx configurations across client servers, I started reaching for Caddy instead. Here’s what changed — and what didn’t.
Read moreMoving workloads to the cloud changes where problems live, not what causes them. Good cloud migrations fix architecture — they don’t just change the hosting.
Read moreGood network troubleshooting isn’t about guessing quickly. It’s about eliminating possibilities in the right order — starting local and following the evidence.
Read moreMore access points don’t fix a Wi-Fi problem caused by channel interference. Adding hardware that competes on the same frequencies usually makes things worse.
Read moreAn unmanaged switch under someone’s desk cost two hours of troubleshooting. Here’s what you give up when you buy cheap — and when it actually matters.
Read moreNot a tutorial. The mental shortcuts and design habits a working network engineer uses to size networks, avoid overlap, and document cleanly.
Read moreThe figure on the box almost never matches the real world. Here’s why VA ratings mislead, why runtime isn’t linear, and how to size a UPS against your actual load.
Read moreRAID keeps systems running when a drive fails. It doesn’t protect against deletion, ransomware, controller failure, or fire. Here’s what backup actually looks like.
Read moreMost home networks aren’t designed — they grow. Here’s how to build one with enough structure that the next several years of changes don’t force a complete rethink.
Read more