a good attitude and some elbow grease most "failed" FP projects I've seen mostly lack the former - often due to managers or engineers that come on the project

a good attitude and some elbow grease most "failed" FP projects I've seen mostly lack the former - often due to managers or engineers that come on the project after it first hits prod then comes the rewrite to add a notch in said managers' and engineers' belts then the original FPers leave and now there's systems in prod with little to no people who can work on it. that rewrite suddenly got a lot more business-critical! the original FPers weren't as PM-savvy, so the rewrite is successful despite having less functionality and still taking a year or more. doesn't matter - the savvier managers and engineers know how to set goals & milestones that they know they'll hit and can say that they hit when evaluating the project's success This is just a summary of my years of experience as an FP professional. I've seen this happen 3+ times across 3+ companies. --- Haskell is by far the most worth-it skill I've cultivated. It wasn't easy but I really do do a 10x job on my personal projects in large part due to it. It's just not a good language to use in a corporate setting. It's better to get paid big bucks to be less productive. Save the technical brainpower for things you yourself find valuable :) (and I sneak Haskell in all my jobs anyways - scripting, for instance - so I still develop my Haskell knowledge on company time & dime, despite the language being all-but-banned by the higher-ups)