1. 9
  1.  

  2. 7

    Looking for a “Haskell job” is the wrong mindset. Look for problems that are amenable to Haskell’s strengths and then find work on those problems with people who are open to using solutions that demonstrably exceed the projects needs.

    The problem I’ve personally had hiring Haskellers is that there are too many hobbyists who try to turn work projects into experiments in the latest type-level programming technique, and end up burning through massive amounts of time and capital trying to solve problems that don’t really add value to the business.

    1. 4

      Good advice, though alternatively, you could simply try your next commercial project in haskell (Or any language you wanted to work in). I do agree that theres a big element of risk involved, but most of that is mostly about starting a new company, not using a rare language.

      1. 3

        Moreover, there’s already a number of companies using it for all kinds of things with success:

        https://wiki.haskell.org/Haskell_in_industry

        Very diverse usage. Most gripes we see are minor stuff if the product is pretty focused with the pluses, esp concurrency and reliability, being huge. Seems to be a high trust in GHC so far among its professional users. Or they’re cherry picking. I can never know for sure with these things being non-specialist. ;)

      2. 2

        This could be titled “How to Get a Job Using Your Favorite Language” given advice should work for most of them. COBOL on mainframes being an exception as you dont want to look too smart in interview: such people tend to leave after a few months of that stuff. ;)