Aug 11

Now why didn’t I think of this?

James Lileks has come up with an idea that should have occurred to me in 1989. In a column about his daughter’s third birthday, he writes:

I got her a car. A real one. No, she can’t drive it; she’s only 3. I’m just thinking ahead 13 years when she hints that a car would make a great birthday present.

I already got you one, I’ll say. You never used it.

Alas, it’s too late to use this trick on Ruth. Anyway, we already told her that she has dibs on the ’95 Neon when she gets her license. Oh, well. (But maybe Ruth can use the idea on her children.)

Aug 06

Hiatus

It’s been over a month since my last post here, and I’m not sure when I’ll be able to return to regular blogging. This is not from lack of interest, but lack of time and energy. I’ve recently had five weekends in a row when I was either out of town, involved in all-day activities, or sick. I’ve found that this sort of thing does more than just screw up your weekends; it also pushes all of the usual weekend tasks like laundry and yard work into the weekday evenings, ensuring that you have no spare time at all. And to make life even more exciting, several of my projects at work have become quite demanding, causing me to stay late on weekday evenings.
Yeah, yeah. Nobody wants to read a litany of excuses. But I thought I should post something here to let my readers (assuming I still have any) know that I haven’t given up, and I will be back.
In the meantime, here’s a link to a bunny with pancakes on his head. His name is Oolong, and you can see him balancing lots of other things on his head at this site.

Jul 02

More crash tales

On second thought, I believe some of my other car crash stories may be worth telling. They’re not dramatic, but some of them are amusing, or at least instructive. I was still trying to decide about this when, while driving to work this morning, I received an omen: as I watched, a car in front of me ran a red light and sideswiped another vehicle. (Nothing serious; no one appeared to be injured.) All right, I’m not completely dense. If the gods want me to write more about this, I’ll oblige them.
As a teenager, I was not a particularly good driver. (In fact, it took me three tries to pass the road test for my license. This was not entirely due to my mediocre driving skills; on at least one of those occasions, the examiner had such a thick Southern drawl that I couldn’t understand most of what he said — and I was born and raised in the South.) The first collision I was ever involved in was an example of my ineptness behind the wheel. I was attempting to park my parents’ 1964 Rambler station wagon, and clipped one of the adjoining cars because I misjudged the length of the Rambler’s hood.
My second crash involved Bob’s paper route. In his essay on the subject, Bob mentions that he often wheedled our parents into helping him fold the newspapers or even taking him on his route by car, but he apparently doesn’t remember that I got dragged into those activities as well. On one occasion, I was driving him around the route in my dad’s 1967 Fiat 500 when I managed to hit another car. Now, in terms of the traffic laws, there is no question that this was my fault, inasmuch as I was driving like a complete idiot when it happened. The route required Bob to deliver newspapers to customers on both sides of the street, so the sensible thing was for me to drive up one side and down the other. But that would have been far too time-consuming. Instead, I was weaving back and forth in order to cover both sides in a single pass. (How did Bob deliver papers to the left side of the street when he was sitting on the right side of the car? He threw them over the roof or across the hood.)
In my defense, I have to point out that we were on a quiet residential street with virtually no traffic, so my driving wasn’t quite as insane as it sounds. But it was pretty stupid. However, I think the other driver wasn’t terribly smart either. If you see a car that’s swerving all over the road as if driven by a drunken imbecile, your first thought is to keep your distance, right? You don’t wait until it’s on the wrong side of the street and then try to pass it on the right. But that’s what the other driver did, and as I swung the Fiat back to the right side of the road, it struck the left side of the passing car. Nobody was hurt, but the other driver was pretty annoyed. And Dad wasn’t very happy about the Fiat, which now had a dented right front fender.
Oh, well. I blame the whole thing on Bob, because none of it would have happened if he had delivered the stupid papers on his bike like he was supposed to.
My third crash was probably also my fault, but I’ll never know for sure. I was driving through a busy intersection (Cherry Road and Charlotte Avenue in Rock Hill) when another car turned left in front of me and I ran into it. The police concluded that I had run a red light. I certainly hadn’t done so deliberately, but I thought it was possible that I had mistaken a green left-turn arrow for a green light. This time the poor Fiat got a dented left front fender. (I’m embarrassed to say that the exact same thing happened to me again in 1995, although this time it was at the most dangerous intersection in Cary, where Walnut Street, Buck Jones Road, and Highway 1 all meet. Again, I had no way to be sure exactly what happened — but I think it was probably my fault both times. And when a very similar wreck happened right in front of me this morning, I knew the traffic gods were trying to get my attention.)
I do have some stories about collisions that weren’t my fault. Here’s my favorite: I was in a Ford Pinto that got rear-ended, and I lived to tell about it. Yes, a Ford Pinto — the car made famous by a design flaw that frequently caused it to explode when rear-ended. My parents bought one in 1976, so it was one of the cars I got to drive after I got my license in ’77. A year or two later, the Pinto was stopped at a red light in Charlotte with me behind the wheel when another car ran into it from behind. It wasn’t moving very fast, so the other driver apparently intended to stop behind me and just didn’t do so quite soon enough. Whatever the reason, the driver panicked — the car backed up, swerved around the Pinto, ran the red light, and zoomed away at high speed. I turned off the Pinto’s engine, got out, and walked back to look at the damage. There wasn’t any. I couldn’t find even a scratch on the Pinto’s rear end. However, the road behind it was littered with pieces of plastic front grille. The Pinto’s notoriously weak rear bumper had not only withstood the impact, it had destroyed the front of the other car! Since the intersection was deserted and there were no witnesses, I just got back in the Pinto and drove away.
There’s another story about a rear-end collision that predates all of the ones above, because it happened before I started driving. Once, when we were both in high school, Virgil was giving me a ride in his pickup truck. A friend of ours was following us in his car. Apparently he was following a little more closely than he should have, because at one point Virgil stopped the truck and our friend’s car bumped it from behind. As the truck jolted forward, my head bounced off the rear wall of the cab, just under the rear window. (I was only 5’6″ tall in those days.) Once we regained our wits, Virgil determined that there was no visible damage to my head — but there was a noticeable dent in the metal of the truck where my head had struck it.
My most bizarre story is about the 1990 collision between my 1982 Toyota Tercel and another car, neither of which was running or occupied at the time. The Tercel was parked at the curb in front of our house in Cary when a teenager who lived in the cul-de-sac across the street tried, with the help of a friend, to start his stalled car by rolling it down the hill and popping the clutch. While the two of them were still pushing the car, it got away from them, rolled down the hill by itself, and crashed into my Tercel. (It’s a good thing the Tercel was there; otherwise the teenager’s car might have jumped the curb, continued down the hill, and ended up in our living room.) Reporting this crash to the auto insurance people was lots of fun. “What do you mean, no drivers were involved?” Fortunately, the hapless teenager and I had the same insurance company, which simplified the claim paperwork considerably. The company was so pleased that they waived the deductible and paid the entire cost of repairing the Tercel’s crumpled fender.

Jun 26

Wheels up

Bob is disappointed that his car crash stories didn’t prompt the rest of us to post similar tales of our own. Well, I can’t speak for anyone else, but the reason I didn’t follow suit is that I only have one dramatic story about a car crash, and I already told it. The other collisions I’ve been involved in were all uninteresting fender benders, with one exception. And that one wasn’t dramatic or life-changing; in fact, it’s really kind of comical. But it does have some relevance to Bob’s stories, so if it will make him happy, I’ll describe it.
I usually begin this story by mentioning that I have never received a speeding ticket in my entire life, and then conceding that the truth of this statement depends on exactly how you define “speeding ticket.” To most people, the phrase means that you were driving faster than the posted limit, a cop saw you or detected you on radar, and you were pulled over and issued a citation. This has never happened to me, for the simple reason that I don’t speed. Okay, I do occasionally exceed the posted limit for a moment while passing, or to get out of the way of someone who’s trying to merge into my lane — in other words, when I think it would be more dangerous to rigidly adhere to the speed limit. But I don’t cruise along, mile after mile, at an illegally high speed.
However, I did receive a ticket in the summer of 1982 for “driving too fast for conditions.” The officer who issued the ticket did not actually observe me driving, or pick me up on his radar. In fact, he wasn’t even there when I allegedly did it; his inference was based entirely on his analysis of evidence at the scene. His most significant clue was probably the fact that the Domino’s Pizza delivery car I had been driving was upside down in a ditch.
What happened was this: I was returning from a delivery run on the outskirts of Rock Hill, headed back to the Domino’s store a few miles away. India Hook Road was a bit wet from a thunderstorm earlier in the day, but the storm had passed and the sun was shining. I was traveling at the posted speed of 35 miles per hour, which is actually quite conservative on what, at that time, was a lightly traveled two-lane road at the edge of town. That particular stretch of road is straight and level, so it wasn’t immediately obvious when I lost control of the car. When you’re driving in a straight line, hydroplaning doesn’t actually change things very much; it just means that if you decide you want to stop traveling in a straight line, you can’t.
Gradually, I became aware of two things: turning the steering wheel had no effect, and the car was slowly drifting off the road to the right. This was preferable to drifting left into the oncoming-traffic lane, but not much better — to the right of the road was an embankment that sloped up steeply. What would happen when the car’s front bumper hit the face of that embankment? I watched in a kind of surreal fascination as it loomed closer.
The result was probably the dullest and most anticlimactic car wreck in the history of transportation. The car slowly performed a counterclockwise half-roll and then slid to a stop on its roof. I found myself hanging upside down from my seat belt. After releasing it, I crawled out the driver’s side window. (If I had been thinking more clearly, I would have gone out the other side; the driver’s window was now on the right side, pressed up against the embankment, but I wriggled out anyhow.)
The first thing I saw, mere seconds after emerging from the overturned car, was a tow truck. It was pulling a boat — the owner of the towing service and his son were inside the truck, and they had been returning from a trip to the lake when they just happened to pass by the spot where I had flipped the car about thirty seconds earlier. (Either tow truck drivers have a sixth sense that draws them to where accidents are about to happen, or the gods of probability have a sense of humor.) He gave me a ride to the nearest phone (so I could report the accident to the police and my Domino’s store) and then found a place to park the boat so they could use the truck to tow the delivery car to a repair shop. Meanwhile, a cop arrived on the scene, took one look at the inverted vehicle, and wrote me a “driving too fast for conditions” ticket. I didn’t agree with this assessment, but saw no point in arguing.
As you might imagine, people who drive tow trucks for a living have a lot of experience with cars that are upside down in a ditch, and putting such a vehicle back on its wheels is no trouble at all for them. Since the car had not actually collided violently with anything, the damage was amazingly light. In fact, the repair shop determined that there was no damage to the frame at all, and only minor dents to the right front fender, which had actually run into the embankment. Even the roof was unharmed. All the oil had leaked out (through the fill opening and/or dipstick tube, I suppose) while the car was upside down, but after a quick refill, the car was perfectly drivable. It required no repairs at all. The Domino’s manager decided not to bother having the minor dents fixed, and we continued to use that car until I left to go back to college at the end of the summer.
I did warn you that this wasn’t a dramatic story. I’ll follow Bob’s example and close with a list of points worth noting.

  • Water is evil, yes.
  • The laws of probability are definitely distorted in Rock Hill. Like Bob, I found that every single person I knew had driven by while I was standing on the side of the road in my Domino’s uniform next to an upside-down Domino’s delivery car. And they all said “That was you?” when I told them about it. Actually, maybe people in Rock Hill just say that whenever you tell them anything. Someone should look into this.
  • Does the music keep playing? Actually, the pizza car didn’t have a radio, so I have no idea.
  • When the court date for my ticket arrived, I went before the judge and pleaded nolo contendere rather than admit guilt. Well, okay, I said “no contest.” Using the Latin phrase in traffic court would have caused the judge to roll his eyes and throw the book at me.
  • The car came to rest just a few yards from a Rock Hill city limit sign, creating a bit of a jurisdictional dilemma. The Rock Hill police officer who was first on the scene had to call the sherriff’s department, because the incident was outside the city. What would have happened, I wonder, if the car had slid a bit farther and stopped right on top of the city limit? (I probably would have ended up pleading nolo contendere at the World Court in the Hague.)
  • I want to point out that although I flipped the Domino’s car, I did deliver the pizza on time.
Jun 25

Makes AdSense to me

Google AdSense is an advertising service that allows Web publishers to sell ad space on their Web sites. What’s interesting about it is that AdSense scans the content of your site and then guesses what sort of advertising is most relevant. And thanks to Google Weblog, you can find out what ads AdSense would place on your site — just enter your URL and click the Go button.
Of course I couldn’t resist trying this. I punched in the URL for this blog, and then reloaded the page several times to get a representative sample of the ads that AdSense thinks belong here. It came up with the following:

  • Star Trek stuff — books, games, items for sale on eBay, and Star Trek: The Experience.
  • Star Wars DVDs.
  • Dungeons & Dragons books and other D20 role-playing game products.
  • Movie posters.

Star Trek, Star Wars, eBay, D&D, and movies. That’s so accurate it’s scary. Perhaps AdSense bypasses your Web site and just reads your mind!

Jun 14

Chicken scratch

I agree with everything Bob says about the uselessness of cursive writing, but I have a few points of my own to add.
Although the real-world advantage of cursive is that it tends to save time by sacrificing legibility, that’s not what the teachers have in mind when they force students to learn it. If you look at the textbooks, handouts, and chalkboard examples in cursive class, what you’ll see is penmanship, the sort of elaborately ornate cursive that no one actually does because it takes far too much time. (It’s art disguised as writing, really — but if that’s what you want to do, why are you fooling around with a ballpoint pen? Buy a calligraphy set and learn how to do really ornamental writing.)
I believe these teachers are motivated by nostalgia for a bygone era when people wrote on parchment with quill pens, and the writing was elegant and beautiful because nobody could write except aristocrats, scholars, and clerics. The scholars and clerics had plenty of time for fancy writing because that was their job, basically. The aristocrats had plenty of time because their slaves did all the actual work, and they didn’t do their own writing anyway — they dictated their words to a scribe or secretary. In other words, the cursive fetish is motivated by a nauseating mixture of cluelessness, elitism, historical ignorance, and feckless longing for the Middle Ages.
I can testify from personal experience that these teachers are warping their students for life. When I taught freshman writing classes at the University of South Carolina, I told my students that they were welcome to turn in handwritten essays, but only if those essays were printed (for legibility) and written in pencil (so they could correct mistakes and make changes by erasing, not scratching out). They ignored me and wrote their essays in ink, using sloppy, unreadable cursive and scratching out their mistakes. I repeated my requirements with increasing vehemence, but my students paid no attention. It eventually dawned on me that it was impossible for them to do what I was asking. They had been indoctrinated for years with the notion that civilized, educated people (i.e., the landed gentry) always used cursive and wrote in ink. When I told them to do the exact opposite, I might as well have been asking them to come to class naked and sit on the ceiling. It was so alien a concept that they simply couldn’t grasp it.
Isaac Asimov once made the same point about Roman numerals that Bob does about cursive writing. The Arabic numbering system is vastly superior to the Roman one in every conceivable way, so why are we still wasting class time teaching kids how to use Roman numerals? What good are they? Roman numerals are still in use, but only when someone wants to be pompous, pretentious, and obscure. I think the motivation is the same as for cursive: elitist nostalgia.
And don’t even get me started about long division.
UPDATE: A few days after I posted this article, blogger Donald Sensing linked to it, referring to me as a college professor. I e-mailed him to explain that I was just a lowly graduate instructor when I taught English 101, but he never acknowledged the correction.

May 21

May the phone be with you

The moment I noticed today’s date, I immediately said to myself, “Hmm, it’s the twenty-third anniversary of the premiere of The Empire Strikes Back.” Now, how did I know that? Sure, I’m a world-class geek, but I don’t normally have information that obscure at my fingertips. In fact, I can’t tell you the exact premiere date of any other Star Wars movie, even the one that came out last year. So what’s the explanation?
It’s the result of a clever marketing ploy by Lucasfilm. Movie studios are keenly aware that to maximize interest in a soon-to-be-released movie, their promotional campaign should gradually reveal tidbits of information about it as the premiere date approaches. Nowadays, the most effective way to do that is with an official Web site, but that wasn’t an option back in 1980. So the studio made use of another network: the telephone system. Lucasfilm set up a toll-free phone number that fans could call to hear plot teasers about The Empire Strikes Back, delivered in character by the voices of the cast. The messages were rotated on (as I recall) a weekly basis, encouraging the fans to call the number repeatedly to make sure they heard each one. And in a stroke of marketing genius, the phone number was the release date of the movie: (800) 521-1980. This ensured that, having memorized the number, Star Wars fans were also committing the date to memory.
I still have that number memorized, even though the line was disconnected over two decades ago. I can’t dial my wife’s office number without looking it up first, but I’ll remember Darth Vader’s phone number until the day I die. Such is the power of fannish obsession.

May 19

It’s dead, that’s what’s wrong with it

In nearly three decades of playing and working with computers, I thought I had experienced just about every way in which they can malfunction, from hard disk failures and faulty power switches (my Gateway Essential 550 did both of those) to chronic operating system instability (Windows 98, I’m looking at you). I’ve even dropped a Palm on a hard floor and heard the sickening tinkle of glass as its screen shattered. But my office computer surprised me today with a new variety of disaster.
Remember what happens on Star Trek when a decloaking Romulan ship attacks, or an overlooked gravitic mine detonates nearby? Sparks fly from the consoles on the bridge, and the air fills with smoke. It was like that. Well, okay, not quite that spectacular — but the computer gave off a bright flash and the snapping sound of an electric arc. As the air filled with the pungent smell of ozone, the computer went dead. Something had shorted out in the power supply, and now I had a rectangular beige doorstop. This computer is no more! It has ceased to be! It’s expired and gone to meet its maker — hang on, IBM is its maker. Well, anyway, it’s definitely an ex-computer.
My coworker in the next office submitted a repair request on my behalf (that’s normally done online, so I was certainly in no position to do it). The “doctor” will come to my office tomorrow morning, but we know the patient is dead and can’t be resurrected. The best prospect is a brain transplant; he’ll bring another computer with him (actually, I think his hunchbacked assistant will be carrying it) and will attempt to swap the hard disks, then channel a bolt of lightning through the lifeless body. (Isn’t that what happens when you turn on the switch?) The result will be a kind of zombie version of my computer, which will shuffle around the office making incoherent noises until a mob of my coworkers gathers, brandishing pitchforks and torches, and . . .
Sorry. Anyhow, the deceased computer should be either repaired or replaced tomorrow.

May 10

Brown paper bags

Ruth says that she plans to take some brown paper bags to the prom in case she and her friends get bored. This is an excellent idea. In addition to the “lookin’ at a thing in a bag” joke, the bags have lots of other uses:

  • Inflate a bag and then burst it to make a loud bang, causing the chaperones to call the police because the prom is being attacked by terrorists.
  • Walk up to a guy you don’t like, hand him a bag, and tell him it’s for his date to wear over her head. Then run.
  • If you get overexcited while doing these things and start hyperventilating, breathe into a bag until you recover.
  • Wear a bag over your own head (with eyeholes, of course) to avoid being identified while carrying out other pranks.
  • If there are any bags left when the prom is over, use them for the time-honored flaming dog crap joke on the way home.

I’m just speaking hypothetically here, of course. I’m sure Ruth won’t actually do any of these things.

UPDATE: Ben points out that Flaming Dog Crap would be a good name for a rock band. (It’s an excellent description of several rock bands I could name.)

May 09

Wrong, wrong, wrong

Instead of an essay on a single topic, I have several items to report today. However, these items do have a unifying theme, which is this: I was wrong.
First, an update on my experiment in moonlighting: it was a failure. “How hard can it be?” I asked here when I announced the idea. Pretty damn hard, as it turns out. I lasted a week. It wasn’t just the chronic sleep deficit, or not seeing my family, or the lack of time for anything other than work or sleep. What finally convinced me to give up was the realization that I had decided to try moonlighting for two reasons, and neither of them was valid. Reason one, you may remember, was that I didn’t want to leave Perigee shorthanded just when their workload was heaviest. But the workload actually peaked a week or two before I started my IBM contract, and Perigee was already starting to lay off temporary workers. By the beginning of this week, the night shift was down to just a few people, and the stuff I was being given to do was pretty trivial. They didn’t actually need me very much.
Reason two was that my family could use the extra money. But I found that because I was short of sleep, I was hitting the snooze button for longer in the morning, and arriving at work later. No one at IBM seemed to mind, because we have flex time — but I was still leaving on time at 5:00 in order to get to my evening job. I wasn’t putting in a full day at IBM. Since my hourly rate at IBM was much better than at Perigee, missing an hour at my day job in order to work an hour at my evening job was, to put it in mathematical terms, stupid. If I wanted to earn more, I would be better off working more hours at IBM. So this past Tuesday, I resigned from Perigee and went home to spend an evening with my family. My stress level has been declining steadily ever since.
What else was I wrong about? Pedestrian signal lights. On Wednesday, my IBM team went to lunch together at the shopping center across the intersection. And I discovered that I was mistaken about the signal light for crossing Six Forks Road — it does sometimes say WALK. But it had never done so for me — not once! Why? There is a very simple explanation. The push-to-walk buttons work just fine, but I was pressing the wrong one. Despite the signs indicating which button was for crossing which street, I had gotten them backwards. I was pressing the button for Millbrook when I wanted to cross Six Forks. How I escaped becoming roadkill, I’ll never know.
If you’re wondering, the restaurant we crossed the street to dine at was the Bull and Bear. Yes, the place that was rated dismal in the one review I had managed to find. Not only had my teammates not read that review, the restaurant is a favorite of theirs; they eat there all the time. Well, I couldn’t very well turn down their invitation, could I? I steeled myself for possible food poisoning and followed them across the intersection. Guess what? There’s absolutely nothing wrong with the place. The service was excellent, and my bean-and-ham soup and chicken cordon bleu sandwich were entirely satisfactory. In this case it was the reviewers who were wrong (or perhaps they just visited the B&B on a bad day). But I accepted their assessment instead of checking the place out myself, so I was wrong, too.
As you can see, I was wrong about pretty much everything. But weblogs can be edited. If I were Michael Moore, I would delete the blog entries showing just how wrong I was and pretend it never happened. Well, I would much rather be like Rachel Lucas. I’ll follow her example and leave the record intact, proving to the world that I’m a moron and I don’t know anything.

Posted in Me