Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Maybe it is because I'm not a Haskell Guru, but although I love Haskell's terseness, it tends to make it very hard for me to read code I've written a while ago. I tend to get excited about cool Haskell features like Arrows, using them whenever I can, then I forget about them, and when I read my code 6 months later, it's like gibberish..


When I find myself using arrows, usually I realise that I got lazy and used tuples because my data model wasn’t good enough. Good code flows from good data.

But really, you should use the “tricks” when they make your code more expressive, not just because they’re cool. It’s the same in any language.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: