Discussion Locked

Dr. Seuss explains: Why computers sometimes crash.

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This bit of humor was written in the style of a Dr. Seuss story to help lighten the stress-filled workday of every IT professional. I thought I would pass it along for your amusement. I don't know the name of the author.

Why Computers Sometimes Crash! by Dr. Seuss.

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, 'cuz sure as I'm a poet, the sucker's gonna hang.

When the copy on your floppy's getting sloppy in the disk, and the macro code instructions cause unwanted risk,
then you'll have to flash the BIOS and you'll want to RAM your ROM, just quickly turn the darn thing off and run to tell your Mom!

8 replies

by juanita marquez

It kind of makes me picture how much harder it is for the average consumer to fix a car. You used to be able to just roll up your sleeves and get greasy, but now they charge you $75 just to hook it up to a computer to tell you whether or not it thinks something's wrong, even if smoke is belching out of the back...

by jamesrl

You can buy the code reader and hook it up yourself. I bought one off a friend, he paid just over a hundred for it new.

You can often find the meanings of the codes on the net, as well as suggestions for next steps.

Even if you want a mechanic to do the work, its good to read the codes yourself.

I only do basic stuff on the car as I don't have a garage or all the tools. I change fuses, light bulbs, top up fluids, will change a wire if its obvious.

by juanita marquez

I actually like tinkering with cars, because normally I can do short projects that make me feel a sense of accomplishment. Nothing major though, mostly things like you mentioned as well as the odd filter, battery, hoses or such. But one of the frustrations of the computer codes is the fact that they go away after turning the car on X times, so by the time you get it to the mechanic, you have nothing to show for it. "REALLY! THERE WAS SOMETHING WRONG!"

I tried changing disc brake pads myself once because in theory that is an easy task, but it's the hydraulics pushing stuff back together while you're trying to insert the pads that I, being a regular woman and not a bodybuilder, had challenges with. Luckily a friend helped out. I will say there are just some things that brute force is needed for and I personally am not cut out for a number of those things.

/me waits for feminist outrage

by seanferd

:p

It's just that attribution where possible is good form. Plus, you get to find out what other stuff the creator may have up the sleeve. ;)

Email - sure- it is like that. I certainly prefer something entertaining, yet without proper attribution, rather than the common apocryphal propaganda/inspirational stories we so often receive.

I now envy you for your email correspondents. :D

This discussion is closed to new replies.