“Automations” are a delusion. Wait lengthy sufficient, and yours will break. It’s virtually assured. And at that time, they’re now not automated. They’re one thing you need to debug and repair.
For that reason, every thing that appears like an automation is basically simply a system that works—for now.
For instance: in our hallway, now we have a stupendous e-ink body. I used Claude to program it to replace each hour. As you’ll be able to see above, it pulls from a number of sources: family chores from an Apple Word, climate radar from Surroundings Canada, circumstances from our yard climate station and Residence Assistant, and extra.
The issue? It breaks always. Our joint Google Calendar disconnects, and I’ve to return into Claude to set it up once more. (It’s damaged within the picture above, in reality!) The home knowledge typically goes clean at any time when our web hiccups. It appears like each a part of it has damaged in some unspecified time in the future. (I don’t care, it’s a enjoyable pastime. I sit up for fixing it the subsequent time it malfunctions.)
It’s not a foul factor that each automation finally breaks. It’s simply price realizing earlier than you construct one.
A number of ideas I’ve discovered useful:
- Guess at the place your automation will break—and the prices of it breaking. This isn’t all the time attainable to know. However begin with the muse it’s constructed on. My dwelling dashboard integrates about 10 providers and breaks always, however I’m okay with this—programming it has been a tinkery pastime. But when it’s mission-critical, look exhausting at every part and the percentages it’ll fail. Know the prices and the dangers.
- Make breakage loud! A silent failure is the damaging variety. So I hold a little bit of “Final Up to date” textual content on the dashboard—when it goes stale, I can spot the break at a look. It’s additionally simple to identify when sections of the dashboard don’t replace. You by no means need to uncover a break by chance.
- Thoughts how annoying it’ll be to repair. There isn’t a lot friction to updating my dashboard—I simply ask Claude once I get an opportunity, both instantly or via the Dispatch function (which lets me message Claude on my desktop from my cellphone). To me that is comparatively frictionless. But when a repair means actual work—like digging up an automatic yard sprinkler—query the muse, and possibly simplify. Fewer shifting elements means much less can go mistaken.
So automate away—however keep in mind what you’re constructing. Not a machine that runs ceaselessly, however a system that works… for now.
