On Python and finishing a thing

If I had to choose my favorite languages they would be lisps, clojure or even ruby. My career has dictated that my specialty with python. I say this because I reallllllly don’t like working with python. I want to use a language that can bend and change and python is not one of them. You can do interesting stuff with it, pandas being an example of making a beautiful DSL within python. But it’s just not what you do with it in a team. I’ve spent maybe 3-4 years working against trying to bend python to what I want it to be. What’s emerged was a feeling that I was using python wrong, backed by a lot of slowness and gripes with python. Where I am now is that I’ve realized it’s my job is to use python. that sounds simple and silly, but it was a big turning point. At work, I don’t use the part of me that wants to make something beautiful. I lean on the part of me that just wants something done and working. I’ve embraced python as a tool that it is. I use it the way it wants to be used. The way other people won’t be surprised by it. And through this, I’ve come to like (not love) python. But I didn’t have to like python to use it well. I just need to understand it. I don’t have to like a programming language to be proficient in it. The liking can come afterwards.