Information Technology Dark Side

Well, he’s really more of an all-around data super genius, but anyway I learned something cool from him:

The Principle of Least Surprise

In other words, if the software could behave in multiple perfectly legitimate ways (based on all the other stuff in the context of the application), then you should go with the one that is going to surprise the user the least.

I like this as a test oracle and as a tool for advocating bugs. In my environment at least, it’s easier to get iffy bugs fixed if I can provide alternative solutions that are easier to understand (i.e. less surprising to the user).

Anyway, thanks to Josh Tolley for the good idea.

PS – Since someone is bound to point this out, let me just acknowledge right away: as a rubyist I should have already been familiar with this.

PPS. Here’s another reference

PPPS. Don’t apply this principle to java libraries. You’ll poke your eyes out and spend the rest of your days in Arkham Asylum.

Stumble it!