Matt Parsons  🏳️‍🌈

Quite measured post. But isn't this just bouncing around the issue of there not being many Haskell jobs. This is the actual problem, not so much the typelevel programming in servant.

I genuinely do think that there would be more Haskell jobs if Haskellers tended to write simpler code, both because you'd need to do more actual work (++demand), and there'd be more potential hires (++supply). I've also seen blown complexity budgets ruin Haskell at a company.

I really like the end goal, but I don't 100% agree with the way. We should strive to educate people on Haskell ideas and tools, and do not overcomplicate unnecessarily. Right now, working on Haskell means being a good mentor and be prepared to explain how some things work.

It's easier to write simple code than it is to push management to allow for more mentoring/training time. Obviously "junior code" is vague and relative, but it's wise to scale that to what you can teach and get someone independently productive on within a month or two.

I definitely agree with the sentiment but it is hard to figure out what this set of things should be, and it likely varies per company

I think the actionable goal here is "Make it easy to hire developers with no Haskell experience."

@_alpacaaa Marco your take is getting cold

Thanks for this, I'm on board with the sentiment too. My codebase with servant, beam, and lenses was more intimidating than I expected to the last developer I tried to onboard (he was just starting out with Haskell fwiw)