Yeah, I haven’t even finished with my entry for Burning Man this year, but this PDF entry should be a bit shorter, so my lazy butt is doing it first.

This PDF was a bit different from previous ones, both in general and for me specifically.  A lot of the planning for it happened at close to the last minute, but everything did manage to come together in time for the event.  I also left my planning to the last minute, but I’m familiar enough with my camping gear that I can toss everything together pretty quickly.

I was only there from Saturday afternoon through Sunday afternoon; I worked on Friday and Monday.  While I had arranged for a ride to PDF, I hadn’t found one back on Sunday, a situation I will not allow again.  It was simply too stressful looking for a ride on Sunday afternoon with the prospect of possibly having to call in to work and say I couldn’t make it in on Monday.

Aside from that, the weekend was beautiful.  This was a much more mellow burn than even previous Fall burns.  At other times, I’ve had the feeling of a very active burn—go and do stuff and experience things.  At this one, people set up their camps and proceeded to just hang out.  I had a moment late Sunday morning where I just looked around the site and was nearly overwhelmed by how beautiful everything was.  I felt forced to lay down and rest, for fear that I might explode with happiness.

I didn’t really do a whole lot over the weekend.  I hung out at the Gold Bar, a pastime I can easily recommend to others.  I rangered a bit.  I hung out at Primal Phred.  I watched the main burn.  I hung out in the pavilion.  I had a great weekend with my friends.

And I made Jill very happy by finally consenting to a body shot.  Yes, Jill has drunk a mudslide from my navel.  She seems, oh, slightly pleased about it.

I’m very happy to have gone, even if for but a scant twenty-four hours.

Herein is contained a very oblique sort of rant, and it’s boring too.  Just skip over this entry.  You’ll feel better about yourself.

The MTA runs a number of bus routes.  Each one is numbered.  I regularly ride the 31.

The 31 runs from Penn Station to Halethorpe.  It goes down Cathedral Street, proceeds from there to Lombard Street, to Wilkens Avenue, runs along Maiden Choice Lane, through UMBC, and along a couple of other streets to its destination.  Oh, except that it doesn’t always go through UMBC.  Sometimes it just goes past it.  Oh, and sometimes it takes Leeds Avenue instead of Maiden Choice; this also skips UMBC.  The buses do have signs that indicate which way they’re going, except that they rarely mention whether or not they’re going through UMBC; you get to guess.  And half the time, the signs are broken or so dim that they can’t be read.

And did I say that the buses went to Halethorpe?  Well, sometimes.  Sometimes they go to Halethorpe Industrial Park, which is the same route, but goes a little further.  And sometimes they go to Beltway Business Park, and sometimes they just stop at UMBC and turn around there.  Mostly, this is indicated on the sign.  But when they go to Beltway Business Park, sometimes they turn onto Sulphur Spring Road and sometimes they head through Halethorpe and up Washington Boulevard.  The signs give no indication which of those it is.

So, the bus signs could say: “31: (UMBC|Halethorpe|Halethorpe Industrial Park|Beltway Business Park) via (UMBC|Maiden Choice|Leeds)” and they still leave out information.

Oh, and the schedules?  They indicate which subroute is being used by leaving out times.  Not going through UMBC?  No time in that column.  The bus that goes to Beltway Business Park via Leeds and Sulphur Spring has a schedule that reads: “[5 columns] <time> - - - - <time>” Yeah, all those blanks are really useful for the people catching the bus in the middle there.

And there’s stuff I don’t understand after over a year and a half riding the bus.  I don’t know what to make of the one line that has a time for UMBC, but not for Leeds and Maiden Choice.  There are footnotes on some of the lines.  “A - Via Goodwill” There’s one line with that footnote, and it skips every column between Wilkens & Caton and Beltway Business Park.  If you’re on that route, better hope you catch that one bus.  “F - Via DeSoto Road” Goes that way southbound in the early morning and northbound during the mid-afternoon.  I don’t know why.  “C - Cathedral & Franklin” “D - Charles & Saratoga” Apparently, sometimes the bus doesn’t go all the way to/from Penn Station.  Again, I don’t know why.

So that’s the simple approach adopted by the MTA.  I regularly see people confused by the plethora of meanderings that the buses can take, and I can’t really blame them.  I don’t have a useful alternative, and I can only assume that there are reasons for the current setup, but neither of those stops the status quo from being just the tiniest bit sucky.

Put very simply, Lucifer's Hammer is a book about a comet hitting Earth.  The book takes 640 pages to do this; there’s a lot of detail to the story.  The first couple hundred pages are all pre-comet and set the stage, introducing all of the characters.  (There’s a dramatis personae at the beginning of the book; I found myself referring to it frequently to see which characters were which.)  The strike itself occupies about another hundred pages, with the balance of the book dealing with the aftermath.

As might be inferred from the spacing of events, the book proceeds at a somewhat slow pace, ramping up so gradually that I didn’t notice the tensions in some scenes until I had to put the book down and realized that I was nearly breathless wondering what would happen.  The aftermath is where the meat of the conflicts occur, but the preceding half of the book is pretty necessary to lay the groundwork for later developments.

The science in the book is also good.  Niven and Pournelle spent a lot of time working out the details of a comet strike such as the one presented in the book, and it shows; the science is very thorough and believable.  This was somewhat surprising given how long ago the book was written:  1977.  Much other SF from that far back tends to be very dated, a fate Lucifer's Hammer seems to have escaped, for the most part.

There were some instances where I was reminded that the book was taking place three decades ago.  Racial tensions in the book are a lot higher; while the civil rights movement had succeeded, many people still weren’t accustomed to it, and a couple of the black characters have to deal with some uncomfortable situations.  The technology isn’t as good as that which we have today; while I can’t remember any specific examples, there were some things that I noted would have been different if the story had taken place in our present.  And someone makes reference to NASA’s perfect record of not having any deaths during their missions, a record that, sadly, has been broken a few times since then.

All in all, it’s a very good book, especially for fans of either SF or disaster stories.

Postscript: The copy I read was one I got from a used book store.  It’s the third printing of the Ballantine Books paperback edition, printed in 1985.  The inside cover has the following written on it:

Dec. 21st, 1990

To: Mr. Senior
After I saw that film on meteors I remembered this book.  You can look it over during the holidays.

Best Wishes,
Bob Vandervoort

I haven’t found any more information about who the people named are.

Yes, it’s true.  I hates software.  (Though, as of yet, not very much.)

Yep, get ’em all out of the way in one common place.

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

I hope that’s all clear now.