the important thing when programming in Haskell is to be sure to do nothing
Submitted by metaperl on Sat, 03/19/2005 - 2:00pm.
Spend your time defining and composing. If you are trying to get something done in 2 lines, then you are trying too hard and have not separated out the task fully.
It's hard for imperative-trained programmers to grasp this, but it is vitally important.
- metaperl's blog
- Login to post comments
I don't understand, can you explain this is more detail?
Can you give an example of defining and composing?
my ideas about implementing those algorithms involved lots of state. So when I looked at how definitional their solutions were, I realized what I wrote... I was actually looking at the heap implementation when it hit me
I cant be more specific than this because I never wrote the imperative algorithm.