I automated my life and forgot all the passwords

At my peak I had receipts auto-filed, emails auto-labeled, a script that renamed my downloads, and three services chaining my calendar to my notes to my to-do list. Building the machine was the most fun I had all year.

Every new connection felt like buying back time, and I drew proud diagrams of the whole machine to show people.

What I never drew was the maintenance schedule, because it honestly never occurred to me that such a thing existed.

My watch buzzed when the laundry finished. A script greeted me with the weather before I had looked outside.

The building was the hobby. The running was the problem.

Nobody tells you that automations do not break with a bang. They break with a quiet month where the receipts stop filing themselves and you notice in November.

• An API token expired; I had no memory of creating it.
• A critical login lived in a password manager entry named “test2”.
• One service was acquired, one was sunset, one just shrugged.
• The documentation I never wrote would have helped. So would a naming scheme.

Repairing it meant archaeology on my own past decisions. Half the credentials sat in an account I had abandoned, behind an email I could no longer access.

I had automated away the chores and inherited a sysadmin job. Unpaid, unstaffed, and on call forever.

I shut everything down for a month and reinstated only what passed three questions.

• Does it fail loudly, so I notice within a day?
• Can I explain it in one sentence to a tired future me?
• Is there a manual fallback that takes under two minutes?

Filing a receipt by hand costs me twenty seconds and keeps the map of my own life in my head. The machine saved me eleven minutes a week and billed me a weekend every quarter.

The real lesson was about maintenance. Every system I build now gets a point in its favor for needing nothing from me later.

Boring and visible beats clever and invisible. My systems are stupid now, and they are still standing.