{
  "title": "I Used to Know Which Python I Had Installed",
  "subtitle": null,
  "description": "Last night, Claude sent me downstairs to push the power button on my media server.",
  "lane": "writing",
  "slug": "i-used-to-know-which-python-i-had-installed",
  "url": "https://ajvanbeest.com/writing/i-used-to-know-which-python-i-had-installed/",
  "maturity": "growing",
  "date": "2026-11-18",
  "updated": null,
  "tags": [
    "ai-assistants",
    "personal-infrastructure"
  ],
  "wordCount": 393,
  "readingMinutes": 2,
  "markdown": "Last night, Claude sent me downstairs to push the power button on my media server.\n\nOkay, let me back up: my family and I wanted to watch a show, but the server wouldn't cooperate. I asked Claude to go figure it out. Two minutes later, Claude came back with a job for me: the machine wasn't responding; could I go reboot it?\n\nI trudged downstairs, bounced the box, and let Claude know my mission was complete. It checked that everything was coming back up, babysat a couple services, and let me know we were good to watch our show.\n\nAll these years in tech and here I am again, holding down the power button.\n\nI used to know my home network inside and out. I built the thing. I configured the virtualization, hooked up the storage, and figured out how to make my home NAS go. That was half the fun. These days, I happily hand over everything I can, right up to “push this button” and “plug in that cable.”\n\nIn January of 2026, I made a note about my machines: “What versions of Python do I have installed? No idea.”\n\nWhen I'm building a local tool, I don't much care whether it's written in Python, Rust, or C#. Whatever the robot chooses is fine. I have opinions about who can see my data and what can talk to my network. I want my tools and games to run well. I want to sit down with my family and watch a show.\n\nOne of the biggest wins of turning my tech administration over to the robot is the documentation. The docs I wrote myself were pretty half-assed. Now the agent thoroughly documents its own work. The next time something breaks, a fresh session can read those notes, see how things are connected, and get on with the repair.\n\nRecently, my robot alerted me to a couple failing hard drives. It told me which services the failures could affect and what data was at risk. We moved the data off those drives, and I asked it to suggest and source replacement hardware.\n\nThese days, I seem to have promoted myself to director of my own home infrastructure. Having seen what replacement drives cost, I have a little more sympathy for my leaders at work. My hardware requests always sounded pretty reasonable to me.",
  "html": "<p>Last night, Claude sent me downstairs to push the power button on my media server.</p>\n<p>Okay, let me back up: my family and I wanted to watch a show, but the server wouldn’t cooperate. I asked Claude to go figure it out. Two minutes later, Claude came back with a job for me: the machine wasn’t responding; could I go reboot it?</p>\n<p>I trudged downstairs, bounced the box, and let Claude know my mission was complete. It checked that everything was coming back up, babysat a couple services, and let me know we were good to watch our show.</p>\n<p>All these years in tech and here I am again, holding down the power button.</p>\n<p>I used to know my home network inside and out. I built the thing. I configured the virtualization, hooked up the storage, and figured out how to make my home NAS go. That was half the fun. These days, I happily hand over everything I can, right up to “push this button” and “plug in that cable.”</p>\n<p>In January of 2026, I made a note about my machines: “What versions of Python do I have installed? No idea.”</p>\n<p>When I’m building a local tool, I don’t much care whether it’s written in Python, Rust, or C#. Whatever the robot chooses is fine. I have opinions about who can see my data and what can talk to my network. I want my tools and games to run well. I want to sit down with my family and watch a show.</p>\n<p>One of the biggest wins of turning my tech administration over to the robot is the documentation. The docs I wrote myself were pretty half-assed. Now the agent thoroughly documents its own work. The next time something breaks, a fresh session can read those notes, see how things are connected, and get on with the repair.</p>\n<p>Recently, my robot alerted me to a couple failing hard drives. It told me which services the failures could affect and what data was at risk. We moved the data off those drives, and I asked it to suggest and source replacement hardware.</p>\n<p>These days, I seem to have promoted myself to director of my own home infrastructure. Having seen what replacement drives cost, I have a little more sympathy for my leaders at work. My hardware requests always sounded pretty reasonable to me.</p>",
  "links": [],
  "alternates": {
    "html": "https://ajvanbeest.com/writing/i-used-to-know-which-python-i-had-installed/",
    "markdown": "https://ajvanbeest.com/writing/i-used-to-know-which-python-i-had-installed.md",
    "json": "https://ajvanbeest.com/writing/i-used-to-know-which-python-i-had-installed.json"
  }
}
