@dibblego Oh wow. Thank you, I needed a laugh tonight.
If your best argument is to use this example of "appropriate identifier naming", then I've only this: HOLY SHIT http://doc.scalatest.org/2.0/#org.scalautils.Good …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego it's missing an `orEvil` method -
New conversation -
-
-
@dibblego My goal with the Good/Bad names was to make it obvious when looking at code whether an Or value was "desired" versus "undesired"Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego I wanted to call them Valid/Error, but if you missed an import, Error would mean java.lang.Error, so I settled on Good/BadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego When using Either, I found I always had to pause to think, Right is "the right answer" when reading and writing code.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego I wanted to eliminate the need for that mental cycle by making the "desirability" of Or values more immediately obvious.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego That said, let me point you to different example of "appropriate identifier naming" by complimenting you on one of your names.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego You pointed me to this set of slides: http://dl.dropboxusercontent.com/u/7810909/media/doc/parametricity.pdf … I haven't seen the talk, but I think the slides are pretty clear.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego You show a method named "irrelevant," which I think makes it clear you are trying to say that identifier names are irrelevant.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.