A few year back, an intern on my team was tasked with updating all the instances where we used a certain type of builder function with a replacement that we had written and wanted to encourage our users to use by example. My boss highly encouraged him to write a script to do that task rather than doing it manually, with the argument that even if wasn't any faster overall, it would make the task much less boring that it otherwise would be. That moment stuck with me a lot; a lot of times, we're highly encouraged to be as efficient as possible rather than doing things a way that might be a bit faster but is much more frustrating or boring, and yet we also have a systemic problem of burnout in our industry. Personally, as long as the end result will be the same, I find doing things in a way that will keep me engaged and energetic increases my productivity in the long run, as making the mundane tasks a bit more fun even at the cost of making them take a bit longer will end up making me much more ready to deal with the harder tasks with a mindset that will end up winning back the time lost and then some. (Note that I'm _not_ necessarily talking about something like using a library or framework that could bloat or slow down the final product, since the "end result" is not the same in that case, in which case the difference in the end result needs to be weighed against the potential benefits)