{"type":"page","slug":"building","title":"The kind of infrastructure I like to keep close.","summary":"Home lab, networking, automation, and validator infrastructure, described at the level of intent rather than exploitable detail.","canonicalUrl":"https://jonathantipper.com/building","markdownUrl":"https://jonathantipper.com/building.md","jsonUrl":"https://jonathantipper.com/building.json","updated":null,"content":"## What runs\n\nI maintain a small set of personal infrastructure because it teaches different lessons from building polished software.\n\n- A home lab for storage, media, experiments, and services that are better owned than rented.\n- Home automation for the useful kind of invisible technology: lights, sensors, routines, and the occasional reminder that convenience needs boundaries.\n- Networking and device management because unreliable foundations make every other system feel worse.\n- Validator infrastructure as part of a long-running interest in blockchain networks and Web3 communities.\n\n## What does not belong here\n\nNo IP addresses. No topology diagrams. No private endpoints. No operational details that turn curiosity into attack surface.\n\nThe point is the shape of the work: I like systems that have to keep running after the fun part of building them is over.\n\n## Why it matters\n\nMaintaining infrastructure changes how you think. It makes trade-offs concrete. Reliability, privacy, cost, power, backups, and security stop being abstract nouns and become things that interrupt your evening if you ignore them."}