Personally I get intrigued whenever people talk passionately in a jargon about a subject I don’t know: I want to find out what it is about and what exactly fasc

Personally I get intrigued whenever people talk passionately in a jargon about a subject I don’t know: I want to find out what it is about and what exactly fascinates them. And I want to be fascinated by it as well (if possible), maybe they know something I don’t. So, I get into it and in the end I maybe understand, but I also realise that just by reading it I would have never gotten the complete picture, I had to experience it myself to get there. In the case of Haskell I like it a lot, even though I don’t use it on the job, the insights I’ve had I am able to utilise in other programming languages (C# at my current job) Anyway, even if that was not a possibility, the journey itself was nice. So maybe just try it out with some tutorials? Or don’t if you don’t feel like it By the way it maybe appeals more to programmers who build their mental model around the code itself and not the machine running it. (This is an intuition I have which I cannot back up, but I got to know programmers who have to try everything out to understand it, see how the computer reacts and build their mental model around it, and I know programmers who reason about the code itself, the meaning it has. Maybe this intuition is BS.)