🤔 Ramblings

Open source became critical infrastructure. That success changed what pull request review means, especially for projects like Home Assistant that millions of households now depend on.

A smart home is not magic sustainability dust. The useful part is measurement, local control, and keeping good devices useful longer.

AI did not create the maintainer burden problem in open source. It accelerated it. Contributors are being amplified, but maintainers are still the verification bottleneck.

Developer tooling is part of supply chain security now. Editors, extensions, CLIs, language servers, and AI tools live next to the credentials maintainers use to publish software.

I'm moving to a new place mid-December, and I can't sleep. Not from stress, but from the overwhelming excitement of building a smart home from scratch. Where do I even start? My brain won't shut up about all the possibilities.

People assume my smart home is a futuristic, perfectly automated masterpiece. The reality? Let’s just say… it’s time for some confessions. 😰

I've visited the Consumer Electronics Show (CES) at the beginning of 2025. I spent many hours exploring the "smart home" areas of the expo, and this is what I've noticed and learned about the future of the connected smart home.

I’m kicking off 2025 with some bold resolutions—like finally fixing my own “test lab” of a smart home, going all-in on open-source contributions, and publishing more writing than ever.

This blog is for those people whose daily job is IT-related (DevOps, developers, system administrators, etc) and who are using Home Assistant at home. If you fit that description, you just might suffer from what I call: The enterprise smart home syndrome. When working in IT, you’ll often