Candy, deceptive candy...

So I'm doing my rounds last night, and since it was after the last weekday before Halloween, there was candy a-plenty to be found throughout the various offices I patrol. Big communal bowls of it.

I'm only human. ;)

So as I'd pass a bowl, I'd occasionally snag myself a mini chocolate bar, or some rockets, or whatever. Always in moderation of course.

But... I do patrols several times per night. And each of those little pieces probably ended up to several kilograms of overall sugar fun. I felt gross. :P

The worst part is that I'll probably do it again tonight. I'm the rat that keeps getting shocked, that's for sure. ;)

------------------------------------------------

I was browsing some of my old text files, and I found this lovely gem:

Dr Seuss Explains Why Computers Crash

If a packet hits a pocket on a socket on a port,
and the bus is interrupted at a very last resort,
and the access of the memory makes your floppy disk abort,
then the socket packet pocket has an error to report.

If your cursor finds a menu item followed by a dash,
and the double-clicking icon puts your window in the trash,
and your data is corrupted 'cause the index doesn't hash,
then your situation's hopeless and your system's gonna crash!!!

If the label on the cable on the table at your house
says the network is connected to the button on your mouse,
but your packets want to tunnel to another protocol,
that's repeatedly rejected by the printer down the hall,
and your screen is all distorted by the side effects of gauss,
so your icons in the window are as wavy as a souse,
then you may as well reboot and go out with a bang,
'cus sure as I'm a poet, the sucker's gonna hang.

When the copy of your floppy's getting sloppy in the disk,
and the macro code instructions cause unnecessary risk,
then you'll have to flash the memory and you'll want to RAM your ROM.
Quickly turn off the computer and be sure to tell your Mom!!


Any questions?