Back to work now, but this first

[dianeduane]

I love LOLcats (check out ICanHasCheezburger.com for examples of what these might be, if you don't know). The artform of captioning cat pictures has its own language. (If you don't know a little about this kind of thing, you may as well not bother reading any further here, as the joke to come will hinge on it. The Wikipedia page on LOLcats has a little data. Or see Anil Dash's entry here.)

Anyway, I laughed myself silly when I came across what can only be considered a LOLVader. A most inadvertent one. Look below the cut...

(EDIT: Or don't: it seems I was a little late to the party on this one.) (snort)



A couple of years ago, Jeremy in Shanghai picked up a most unusual ripoff DVD of Star Wars III (the translation of the title of which came out, in this weird dub, as "Episode III, the Backstroke of the West"). The subtitles are... unique. I encourage those of you who love mangled translation to look at them all.

But this is the one that reduced me to helpless laughter for some minutes. Darth Vader (né Skywalker) is producing a great, anguished, (theoretically-) heartwrenching cry of "Nooooooooooooo!" And how does it come out?

Comments

Re: IM IN UR CODE FIXIN UR BUGZ

[keristor.livejournal.com]

Oh, definitely agree about asserts. They are useful in debugging if you want to know immediately if there is an error, typically one which means that it is impossible to continue (things like a null pointer where it should never be null), but they are way over-used. As in this case, where it was indeed a situation which shouldn't happen but it could, and as a result the whole thing stopped with the assert instead of continuing and handling it properly. (The problems of testing with a 'debug' version and then releasing with debugging off is another kettle of finny things.)

I have never used an assert in my own code (as in code written for myself rather than for pay)...

I'm in the UK, and the company have a recruitment freeze at the moment...