Swizec Teller - a geek with a hatswizec.com

Senior Mindset Book

Get promoted, earn a bigger salary, work for top companies

Senior Engineer Mindset cover
Learn more

    Why I still haven't learned Haskell

    Light at the end of the tunnel
    Light at the end of the tunnel

    Short story: because I'm lazy.

    Long story is a bit more nuanced. It involves everything from how many hours there are in a day, how shiny the distractions are and having enough excuses to learn stuff.

    The right tool for the job

    Possibly the biggest reason why I try out new technologies, get super excited, but then never learn them properly is the Use The Right Tool For The Job mantra I've lived by ever since I stopped being a teenager and became bored of religious wars.

    At the end of the day, the client doesn't really care what technology you use, your users don't care about the technology either. They care about a working product that is maintainable, expandable and gives them a good price/performance ratio.

    Now look at my life:

    • Hey, can you make us a complex business-like website on MySQL? - Sure! -> django
    • Hey, we need a glue layer between a bunch of services! - Awesome! -> node.js
    • Hey, I need a script to munge this data into that data. - Hooray! -> python
    • Hey, can you do X with websites for us? - Yep! Finally something algorithmic, I can use Haskell \o/

    Oh wait ... except I can't use Haskell.

    I'm charging you decent money for this, and I'm not really productive in Haskell yet. I can make some cool things with it, but it takes twice or thrice as long as using tools I'm familiar with. Of course you don't want to spend that kind of money to fund my pet learning subject.

    For no obvious gain of course.

    I could just as easily do it in some other language. Except it would be cheaper to create, easier for you to maintain and I'd spend more time on the problem than battling an unknown tool. But it wouldn't be as cool!

    Yeah ... oh and what's that? The best tool for the job happens to be a library that only works in Java? Great.

    And the vicious cycle just keeps repeating itself.

    Because I never know enough Haskell, Haskell never becomes the right tool for the job. There would have to be a very very good reason that goes beyond "I love Haskell! It is the coolest language since forever!" to make me use Haskell on a paid-for project.


    Right, but I could just learn Haskell in my own time couldn't I? Then I'd know it well enough and suddenly it would be the right tool for the job and everyone would live happily ever after.

    Well, no.

    I've tried that:

    1. Learning me a Haskell
    2. Raining datatypes
    3. A message from your future self
    4. Collatz, Haskell and memoization
    5. This Haskell is wrong, why?
    6. Lychrel numbers

    Certainly not a lack of trying to learn Haskell. And I've learned a lot, don't get me wrong. It is most certainly my favourite language for implementing algorithms.

    But at the same time, I still haven't fully figured out monads and doing IO or anything actually too much useful ... it just doesn't come together.

    I mean, there's so many things to learn. So many things to do. There isn't enough time in the day to work on everything and learn everything that I want and love and find interesting.

    As unfortunate as it may be, Solving The Problem mostly comes higher on my list of priorities than* Learn This Cool New Way Of Solving The Problem*.

    Published on June 18th, 2012 in Functional programming, Haskell, Implementations, Java, Languages, Programming, Tools, Uncategorized

    Did you enjoy this article?

    Continue reading about Why I still haven't learned Haskell

    Semantically similar articles hand-picked by GPT-4

    Senior Mindset Book

    Get promoted, earn a bigger salary, work for top companies

    Learn more

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️