[sokoloff]

How common is it for the same person to have both strong Haskell experience and experience building large real-world applications?

I’ve tried to find a way to use Haskell (lacking strong experience there, but with lots of large app experience), and I’ve not managed to find a situation where pulling the trigger makes sense because of the risk of getting “stuck” with a poor path out.

[matt-noonan]

> How common is it for the same person to have both strong Haskell experience and experience building large real-world applications?

I would conjecture that it is more common than what you’d expect from random chance. In my case, I picked up Haskell only after building large systems in C++, Objective C, Lisp, and Python. The draw was that Haskell let me express the kind of system invariants that make it possible to reason about a large codebase.

Since then I’ve written production Haskell in three different companies, none of which appear on this list.

[seddona]

Maybe try contributing to a large Haskell codebase first to get a feel for what Haskell is like in in-the-large and gain some comfort.

I'll add this problem is not at all Haskell specific. If you put an experienced Java developer to work architecting a large Python application where they have no prior Python experience you are going to experience similar problems. I'd say the problem is perhaps a bit more acute with Haskell as the paradigm is likely more different to the prior language. So if possible get at least one person on your team that has experience with a large Haskell app and pair them up with other devs.

[FpUser]

In tech world languages are like a religion. Their choice does not really have to make sense. Hence unless it is 100% total proven failure the affiliates will try any means to protect/advocate/spread whatever language they like.

[Koshkin]

This is an inconvenient truth.