About
I got into this because a computer in my parents’ basement stopped working and nobody was coming to fix it.
That is more or less the whole story. I took it apart, I made it worse, and then after a while I made it better, and somewhere in there I found out that the taking-apart was the part I liked. Everything since has been a version of that with a larger blast radius.
Professionally that has meant backend and infrastructure work — the parts of a system that are invisible when they’re right. Right now most of my week goes to a white-label communications platform: multi-tenant, a lot of data-architecture decisions that will look either obvious or catastrophic in three years.
The rest of it goes to side projects and to the house. I have opinions about DNS, a bench full of test gear I am still learning to use properly, and a network at home that is over-specified for a family of four in a way I will not be defending.
What I actually care about, and the reason Logical Disconnect exists, is the part of troubleshooting that doesn’t transfer well: the order you ask questions in. Most people who are good at this can’t explain how they do it. I’m trying to.
Some honest numbers
- Years writing software
- 20
- Projects actually shipped
- 9
- Projects quietly abandoned
- More
- Countries visited
- 23
- Home network rebuilds
- 4
- Times it was DNS
- Most
