That’s quite a stare.
(via Gruber, via The Singapore Grand Prix – The Big Picture – Boston.com)

That’s quite a stare.
(via Gruber, via The Singapore Grand Prix – The Big Picture – Boston.com)

How long would you have to wait? See you there in 11-16 years!
(via Panda, via Reason Magazine)

I came across an interesting discussion on programming.reddit (the original link and the resulting discussion) about whether or not to use status code as return values to indicate success/failure, as opposed to using exceptions to indicate, well, exceptional cases.
I won’t repeat the pros and cons of either approach, as smarter people than me have done so. One reason for using status codes that I didn’t see mentioned is the ability to easily identify non-failing functions. Imagine you see the following interface:
Status DoThing1(); Status DoThing2(); Void DoThing3();
By observation, you immediately know that the third function simply cannot fail, and no error-checking need be done. The counter argument is of course that if the function declares an exception then you have the same information, but as someone else said, where checked exceptions lie, so do dragons.
As to the title of this post, it was something new that I learnt today about something called the Samurai Principle:
Return Victoriously, or not at all.
That made my day.