IssueRaiser

I think you've got a point there that can be reinforced by looking at the ratio of Haskellers vs.

I think you've got a point there that can be reinforced by looking at the ratio of Haskellers vs. those comfortable with splitting things out to (.) or (>=>) Critically, however, one does not need to be good at abstracting out code in Haskell to be happy and productive using Haskell. We need to be careful not to move on the goalposts on our beginners, it's deeply unfair and frustrating if we make them think they can't do anything at all until they can do it perfectly.

Posted by coolsunglasses on May 30, 2015, 10:29 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments

hackernews (Other)

I think you've got a point there that can be reinforced by looking at the ratio of Haskellers vs.

coolsunglassesMay 30, 2015, 10:29 PM

I think you've got a point there that can be reinforced by looking at the ratio of Haskellers vs. those comfortable with splitting things out to (.) or (>=>) Critically, however, one does not need to be good at abstracting out code in Haskell to be happy and productive using Haskell. We need to be careful not to move on the goalposts on our beginners, it's deeply unfair and frustrating if we make them think they can't do anything at all until they can do it perfectly.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue