|
There’s a special kind of panic that comes when you realize you might have just broken something that really matters. Mine started with one small file — a cryptographic key used to publish a client’s Android apps on the Play Store. We were hours away from handing everything back after years of collaboration with a major client. The transition needed to be clean and professional. And then I couldn’t find the key. See, a few years earlier I had made what I thought was the responsible choice: I only made one copy of the key and kept it safe. For privacy reasons, you just don’t save sensitive keys in a version-control repo. Except “safe” turned out to mean “somewhere only past-me knew about.” When I went looking, the old Skype message where I’d sent it had expired. No one else had downloaded it. My backups weren’t old enough since I migrated computers. My old computer — the one that might still have it — was sitting back home in the UK, boxed up to be sold. That was a very long couple of hours. Without that key, the client wouldn’t have been able to update their apps. Even Google couldn’t help. They would have had to start again with new listings — losing users, ratings, and visibility. Not exactly the graceful hand-off we’d promised. 😬 Luckily, my brother found a copy buried deep in an old project folder. He sent it over, and the crisis passed. But I never forgot that moment. It taught me something I still live by: Security is important.
Resilience is everything.
Automation isn’t just about efficiency. It’s about creating safety nets for your future self — versions, backups, and checks that quietly save the day when human memory doesn’t. We love to think automation makes things faster and easier. But the best automation doesn’t just save time — it saves you when things go wrong. That’s the real magic of automation — it lets you sleep at night. So if you don’t have simple reminders or systems to make sure your “keys” are (literal or metaphorical), maybe it’s time to build that into your setup. Andrew "oops didn't mean to do that" Molloy Want a second pair of eyes on your systems? ✨If your automations aren’t backed up, synced, and documented, you need this. This month, I’m opening a few paid Automation Wizard System Audits — hands-on deep dives that bulletproof your setup, uncover weak points, and make sure future-you never ends up in panic mode again. |
Automation Wizard/Soloneer - Exploring how we can use the latest technologies such as AI, automation tools like n8n, and 3D printing to make our lives easier and better.
The hardest part of building an AI agent system isn't the technology. It's the blank page. You know what you want: an agent that knows its role, stays in its lane, handles recurring work without you micromanaging it. But when you sit down to write the system prompt, you stare at the cursor. What do you actually put in there? Over the past several months I've built a 5-agent council that runs my YouTube production pipeline. There's a CEO agent that sets direction and delegates. A technical...
The Delivery Audit A 20-minute pass over every automation you own, to find the ones running in the dark. Companion to "The automation nobody sees." You don't need any tools open to start. A list andtwenty minutes. Step 1 — List them (5 min) Write down every automation you currently have running. Zaps, Make scenarios, n8n workflows, Kitsequences, scheduled reports, dashboards, recurring exports, anything on a timer. Include the ones you forgot about. Those are the point. If you built it more...
Ten weeks since my last email. The automation guy went quiet again, and this time the reason is a bit embarrassing. I built the AI Agent Workflow Starter Kit and wrote this email announcing it. Then I never pressed send. It has been sitting in drafts for months while I got on with everything else. Turns out being busy is a very reliable way to ship nothing. So here it is, as I wrote it. The hardest part of building an AI agent system isn't the technology. It's the blank page. You know what...