Systemic Actions through Automation

Brett Terpstra in “Judging the value of automation”:

I enjoy the process of building automations in myriad contexts, using myriad tools. […]

I often think about the benefits of automation in the context of time savings. It makes things more efficient, removes drudgery. But I’ve realized over time that the real benefit of automation is avoiding mistakes.

When I automate something (anything), I’m defining the steps that need to be included to complete the task. I’m no longer relying on my memory to ensure that every step is complete or the specific ways in which a step should be completed. This is especially useful if it’s something I don’t do very often […] if it helps me do the exact same thing one time a year later, that’s often worth as much as any amount of total time saved in my life.

Exactly! Avoiding mistakes is much more important than any time-saving¹. Automation removes the need to remember what you need to do, and simplify the sharing of knowledge. It's basically a self-fulfilling checklist that can be triggered by anybody.

---

When I was developing a new website for Pixelnest Studio, the first step was setuping the project, and automating the deployment, so that I could come back 6 months later and still be able to deploy easily without reading the README or the code.

For Steredenn, I created a lot of scripts to automate the release pipeline (building the game, packaging it, creating the different changelogs for the multiple platforms, etc.). This took me a non-negligible amount of time, but when I needed to do a new release after a long hiatus, it was a breeze and such a relief. Bonus: my associate could also do it in case I was not here, without having to dive in the code or knowing the full process.² In the game itself, Damien spent time creating little tools and helpers to go to a specific part of the game easily, so we could test different configurations and situations at will. The result? A better, more stable game. Less mistakes. More time.

I maintain a personal repository with most of my non-app scripts on GitHub, and one of my most treasured part is a procedure to boostrap a new macOS installation in a semi-automated fashion. I don't do that often, but I know that I can confidently reproduce a new environment (in case of loss or theft) without a lot of struggle.

I tried to put most of the settings of my apps (Alfred, iTerm2, Dash, etc.) on a cloud provider, so that I can share them between computers and have a backup (it's actually one of my selection criteria when I try a new tool — "can I sync the settings easily?"). The tools are tailored to my use, and I don't have to customize them again.

I automated and documented our servers installation so that I could nuke and reinstantiate them easily. I'm not an experienced sysadmin at all, so having this ability to restart from scratch was a godsend to me.

It's not pure automation, but it falls in the same ballpark for me. It's emptying your brain so that you can focus on what you care. And, bonus, it's fun to do!

---

As a different example: I scan and store all my documents online (pro or perso). When I'm asked for something (passport? last phone bill?), I take my phone, get the document and send it or print it directly.

It's a really simple process: when I receive a paper, I quickly look at the document, decide if I keep it or not (if not, it's direct in the trash), then launch Scanbot, OCR it and boom it's stored in the right place. It has just become automatic for me now. It takes me literally 10s. And this has saved me so. much. time, as well as prevented the loss of important stuffs. It would have been easier to just put that doc on a shelf and never care about it anymore, sure. But then, when you search for a new flat, and need to find those twenty docs, you will thank yourself.

It was always more effort initially, and we, humans, don't like effort. But being a good slacker is not about doing nothing, it's actually doing more at the beginning, so you can do less later. And that's what computers are good at too!

---

That's also a reason why I love checklists so much. Checklists are the manual version of automation: you write it, you duplicate it, you cross it, and you forget it.

Checklists are also cheap and easy-to-write documentation — for you, your family, your friends, your coworkers.³

---

In computing (and life in general), there are a few principles that I consider extremely important and I'm trying to apply as much as possible:

• Repeatability: repeat a task in a predictable manner and efficiently without dreading it;
• Robustness: ensure you are doing the right steps and actions all the time, constantly. Backup. Use version control and history systematically;
• Shareability: share information painlessly with other people, and more importantly, your future-self;⁴
• Mastery: learn your tools, the shortcuts, and the customization points. Dive in the menus, try everything. This is physical automation: you train your body to repeat stuffs quickly without thinking about it.⁵ You save time, you reduce mistakes, you get better;
• Documentability: enrich your knowledge base constantly - that is vitally important. Document what you do and why.⁶ Take notes, create a task in your todo apps to not forget something important. Offload your mind and find any information in no time.⁷

That's automation, although at a bigger scope than just plain computer automation and scripting. That's why I like to be organized and to create systems⁸ in my life⁹ (and not only on my computers). It's a way for me to be consistent, coherent, efficient and meticulous. To care about what I do without putting more charge on me.

And to be able to lose my time on the areas where it provides me joy.