Programming protip: NAME THINGS. Your long run-on chain of method calls is not “more l33t”. It’s harder to read.
-
@puffnfresh@bitemyapp :-) My example was clearly facetious. I was pointing out how *not* to break things up by name.
@djspiewak @puffnfresh Not sure I support that generalization. I like the readability of, eg
val result = xs map fn filter pred mkString ","
-
-
@propensive@puffnfresh If your operations are part of the same computation, there’s no benefit to naming intermediate steps. -
@djspiewak@propensive everything in my program is part of the same computation. - Show replies
New conversation -
-
-
@propensive@puffnfresh The way I like to differentiate is, “If it’s hard to come up with a name, maybe it doesn’t need one.” -
@djspiewak@puffnfresh That's perfectly fair!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.