Clearly an automator. I simply enjoy it more than purely exploring.
Which doesn’t mean that I don’t enjoy the exploration (and learning) that is necessary for good automation.
I participated in an online poll around this very question 2 weeks ago, it was not asked in a binary form like this though. Not sure what platform it was on. I was a bit surprised by the results - and to be honest making the question binary although creating more clear data, for me, hides the underlying activity cost.
Automator. I do a fair bit of both, but I use automation specifically as a tool to cover more ground and to find certain domains of “watering hole” that bugs with congregate around.
I enjoy exploring but I can’t stay with a single topic/item for too long, so I go from different angles: process, business, statistics(revenue, data, apis, …), analysis(user,finance, call-center, surveys, reports,…), optimizations, code, pipelines, data, UI/UX, external systems, integrations, backward technical discovery, history of changes and decisions, other products within the company, using tools owned by other departments, …and so on.
I also like playing with code.
I noticed recently that I do more exploring than coding when I’m an Automator(in longer automation projects). This is due to the shifting nature of things, the predictability: the data changes, the product is unstable, the code is randomly failing, errors that I trigger in the logs(without seeing there’s a problem), the optimizations that can be done to reduce execution time, debugging failures with various methods, deciding whether I should do some refactoring and how, and so on.