Earlier in my work, I had a habit of scripting everything.
If a task repeated more than once, my instinct was to automate it — write a script, set up a small tool, or build something reusable. In many cases, that made sense.
But over time, I noticed that not every task deserves that level of setup.
Some things come up irregularly: converting a file, extracting a few images, checking a format, or doing a quick transformation that might not happen again for weeks. Writing scripts for those jobs often took longer than the task itself.
Nowadays, I try to be more selective.
If something is part of a regular pipeline, I automate it properly. If it’s a one-off or a short-term task, I’m fine using lightweight solutions just to get it done and move on.
For example, when I need to quickly extract images from a PDF and don’t want to install or configure anything locally, I might use a simple web-based tool like this one:
https://mmtocm.net/
It’s not part of any automated workflow, and I wouldn’t rely on it for large batches. It just fits those moments where convenience matters more than long-term optimization.
Letting go of the urge to automate everything has actually made my work feel calmer and more focused.
Top comments (1)
This really resonates with me.
I used to script almost everything too — even small tasks that only happen once or twice a month. Over time, it just started feeling like the “automation setup” took longer than the task itself. What helped me was mentally separating tasks I actually repeat often from those that just feel repetitive in the moment.
Now I only automate when it clearly saves time over the long run, and I try not to get hung up on optimizing something that’s essentially a one-off. Reading this made me realize I’m not the only one who went through that mindset shift.
Thanks for putting it into words!