{"slug": "automating-my-job-away", "title": "Automating my job away", "summary": "A developer at Microsoft describes how adopting a policy of automating any task done more than twice led to unexpected consequences, including increased context switching and errors, but ultimately enabled new ways of working. The author advocates using AI tools like Copilot CLI to generate automation scripts and skills, even with minimal specification.", "body_md": "I build tools for people\n\n*This post was inspired by conversations with several colleagues: Sourav Pal, Gustavo Soares, the Excel Agent Science Team, John Lam, and Dan Morris.*\n\nI was talking to a friend who runs a [startup](https://certiv.ai/) and he said that he tells his team, **\"don't do anything three times.\"** If they have to do something more than twice, they should automate it.\n\nSurely, this is overkill? I already automated 95% of my coding-related tasks. What else would be left for me to do even? And the remaining bits are probably too hard to automate. But... I was wrong. Very, very wrong.\n\nI started trying it. Slowly at first, because automation can be a distraction from getting work done in the moment. By the second week, I was leaning in head first—*how deep does the rabbit hole go?*\n\nThere was an unexpected consequence: By automating the laborious parts of my work, I had, in turn, filled my day with *more* laborious parts.\n\nA menial task that took me 5 minutes once or twice a day turned into a menial task that I was doing 10-20 times a day. As I had automated the obvious parts, it left behind the glue work that never bothered me before. Now it was a substantial part of my day, and the context switching was killing me. It was no longer a linear step-by-step process since I was juggling several agents concurrently. Because of it, I was now making silly mistakes, which compounded the time and hair pulling.\n\n\"It never gets easier, you just go faster\" — Greg LeMond\n\nTry it yourself: Anytime you need to do something more than twice, spend the *minimal* time possible asking Copilot CLI to automate it. Don't write out a spec or give details or provide examples. Let it try to figure it out. Maybe it will fail, oh well, it is only a tiny bit of time spent, and then you can check where it failed and ask it to correct it.\n\nI'm surprised at how far AI can get on the first try even when under-specified. But don't just generate Python scripts for automating tasks. Your agent should be generating skills so that it knows when and how to use the scripts. You shouldn't be running them manually.\n\nThrough this process, I also learned that automation allowed me to change how I worked, not just speed up my work.\n\nRecently, Karpathy's [autoresearch](https://github.com/karpathy/autoresearch) inspired the world to try self-improving agents. What if we expose a bunch of knobs to the agent and let it experiment continuously? Even better, what if we let the AI come up with new knobs?!\n\n*\"Copilot, read my Copilot session logs from the last 7 days and propose opportunities for automation. Draft a reusable skill for each.\"*\n\n*This article was not written by AI.*", "url": "https://wpnews.pro/news/automating-my-job-away", "canonical_source": "https://austinhenley.com/blog/automatingmyjob.html", "published_at": "2026-06-14 03:05:12+00:00", "updated_at": "2026-06-14 03:30:06.377177+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "developer-tools", "ai-agents"], "entities": ["Microsoft", "Copilot CLI", "Sourav Pal", "Gustavo Soares", "John Lam", "Dan Morris", "Karpathy", "autoresearch"], "alternates": {"html": "https://wpnews.pro/news/automating-my-job-away", "markdown": "https://wpnews.pro/news/automating-my-job-away.md", "text": "https://wpnews.pro/news/automating-my-job-away.txt", "jsonld": "https://wpnews.pro/news/automating-my-job-away.jsonld"}}