Whining and Dining

St. Michaels, Maryland

 

Steve sent a text saying if I arrive in time, meet at the Chesapeake Crab and Steakhouse for dinner.

There I found him, with Webb, Curt, and Tom. First order of business was to recount how each of us had come here.  Tom had trailered his Pathfinder 1300 miles all the way up from the Florida Keys. Webb, of course, had sailed in Gannet most of the way around the world to get here, dodging a hurricane on the way. Steve started in Cambridge and sailed Spartina for two weeks on a circuitous route of about 300 miles. Curt started on the western shore and sailed Annie across the shipping channel in the dark from Shady Side, Maryland. I weathered DC rush hour traffic towing a boat and risked aggravating Homeland Security.

 

Raked masts

 

So, for all of us, the trip to St. Michaels was an adventure of trials and tribulations. Being mariners all, some of us approaching ancient, the telling of the tale is part of the package. Mine would have seemed more adventurous in other company. Except perhaps for Tom, though, all would choose their tribulations over mine.

After dinner I found Dave Gentry and pitched a tent in the dark and rain. The campsites had filled up more than I’ve seen on a Thursday. I understand they had the most people ever on the Wye Island gunk hole trip. And Kristen, the museum president, was on her way back from solo-ing in a kayak for 60 miles around Kent Island.

 

 

 

Steve’s Pathfinder “Spartina” bedded down.

 

Friday morning was cool and breezy as a front blew out the rain. Good sailing. Took a bunch of photos of boats along the docks, then launched Caesura and spent the day on the water, returning in time for the traditional festival kickoff of steamed crabs and raw oysters.

 

 

 

 

 

How Not to Drive to St. Michaels

The Intersection, DC at Rush Hour

 

link to Google Street View

 

I’m going to tell you about the fine time had at MASCF this year, I swear. First you have to hear about the terrible time getting there.

On a good day, the drive would take four hours. On this day it took six.

Things were still going fine when I passed Dave Gentry in Fredericksburg. He had two of his skin-on-frame canoes on top of the car, so was easy to spot. A honk and a cheerful wave. Dave only lives a couple of miles up the road, but somehow we meet more often at boating events than around town. (Neither of us is sure this is a bad thing.) He was also enroute to St. Michaels.

We’re running a little late. Anyone who lives anywhere near Washington, DC, knows you don’t want to be within 50 miles of it during rush hour. Which is more like rush four hours – it starts at 3 and lasts to 7. But with a little luck we’d be on the far side of DC by the time the worst traffic ramped up. That luck went the other way, literally.

If you use mapping apps, you know software engineers keep trying to make them smarter. For years they’ve tracked the speed of cars moving slower than normal and warn you when there’s a problem ahead. Gives you the opportunity to plan your route differently. Very handy.

Then they started suggesting alternate routes while you’re underway. This was more intrusive, but still helpful. In Google Maps, the voice assistant would say “Tap if you want to accept this new route.” I rarely took these alternate routes, because the time saved was minimal, and it was dangerous to try to grab the phone while driving and find and tap the button before it disappeared. Just wasn’t worth it.

Well, apparently, that function changed with the last update. Now, regardless of what route you planned to take, Google will automatically reroute you. That’s the default. Now the message says, “Tap if you don’t want to accept the new route.” There are multiple problems with this. Let me innumerate them:

  1. The option to reject the new route only lasts a few seconds. That means you MUST grab the phone, find the button, and reject it quickly. Every time it attempts to reroute you. Otherwise, within seconds it’s sending you off in some other unknown direction. This is dangerous, and contrary to the user’s wishes.
  2. More and more people are using these apps, even when they already know where they’re going, specifically to get the traffic updates. That means Google is routing ALL those people onto the same alternate “faster” route at the same time. A side road designed to handle local traffic instantly becomes overwhelmed and gridlocked with cars, as though a big river were suddenly diverted into a creek. These apps are NOT managing traffic flow overall, they’re optimizing the route for each car as an isolated individual, irrespective of the cumulative effect that rerouting all those individuals will have when it happens in unison.
  3.  Problem is amplified by the core issue, which is these apps are not basing their recommendations on a predictable future. They are not looking at the bigger picture, or even using basic statistical probability to make smart decisions. They are at best giving you directions based on reported conditions already in the past, conditions that change very quickly. Effectively they look at somewhat recent reports and take you off what may now be a perfectly acceptable highway ahead, to send you and ten thousand of your closest friends onto a tiny side road in a residential neighborhood. All at once. And this is now the default. You have to take immediate action to prevent it. Every time that it thinks it knows better.

I did not know these things as I blithely wended my way towards the gaping maw of our nation’s capitol. The app worked fine before.

So at 3:30 when the little voice assistant said, “There’s a slow down ahead. You can save 11 minutes by taking this alternate route,” I ignored her to reject it. Moments later, I suddenly found myself in an exit only lane on my way toward the Pentagon, which closes at 3pm precisely because the 23,000 people who work there swamp all of DC with traffic so badly, all by themselves, they have to close early.

I, as a human with a modicum of experience, knew this. Apparently, the app does not know this. And does not know that with excruciating predictability the traffic in DC is about to explode. Nor does it know that I am towing a boat on a trailer. I, however, do know this.

Within moments I’m penned in on all sides next to the Pentagon by angry aggressive drivers, caught like a stick in a current flowing right toward the center of DC and the National Mall.

  • Yes, I saw the 9/11 Monument.
  • Yes, I saw the Washington Monument.
  • The Jefferson Memorial.
  • Lincoln Memorial
  • US Treasury
  • Smithsonian
  • Air and Space Museum
  • Museum of the American Indian
  • National Botanic Gardens
  • Library of Congress

AND

  • The US Capitol Building

Well, I would have seen the Capitol, except Google didn’t know I was towing a boat on a trailer, and I didn’t know that since 9/11 trailers are not allowed on Independence Avenue within several blocks of it. I found out this little detail when, around 4pm with the roads jammed with cars, police suddenly swarmed off the sidewalk toward me waving their arms and blowing whistles, and a patrol car whipped out across six lanes of traffic to block my way with lights flashing and sirens whooping.

There, in the middle of an intersection, blocking a total of nine jammed up lanes of angry traffic, surrounded by armed police persons, it was explained to me that I could not move one foot further forward.

They cleared the intersection and made me do a 270 u-turn right there, with the trailer, heading off somewhere into south DC and into the narrow one lane neighborhoods of Capitol Hill. All the while Google kept saying “Rerouting, make a u-turn, return to the route,” trying to send me back to the armed police officers.

From the time Google Maps took me off the highway to save 11 minutes, it took me 2 hours to get out of DC and back to where I would have been if I’d just stayed on the route planned.

Around dark, as I was rolling into St. Michaels, Dave Gentry called to see where I was. He had just arrived. He, too, had been rerouted into DC along the same “faster” path.

 

 

 

Salient Saline ~ video

 

direct youtube link

 

Some video from sailing with Steve near Gwynn’s Island, with a snip from the night before as he was motoring off to anchor under a full moon for the night.

 

 

Salient Saline

Steve alongside in Spartina

 

Steve and I have been trying to get together again for over a year. Work or weather always interfered. An unexpected cool front brought clear skies and gentle breezes this weekend, unusual for August, and we finally managed to pull it off. I wrapped work stuff up Friday at noon and threw some gear in the back of the car, hooked up a boat to head for the coast.

For a change we met in Tidewater, on the Rappahannock at Gwynn’s Island, where he and Curt and I spent a day on Curt’s Drascombe Lugger, Annie. It’s also where Doug and I sailed both my Melonseeds when he was visiting from California.

 

 

Apparently the posts I’ve shared about a restaurant on the water nearby peaked Steve’s interest, so we met there, I hopped aboard, and we sailed around a bit on Spartina,

Funny thing about when Steve and I go sailing: we don’t talk much about boats. He’s well-read, and we have similar tastes, but different enough that I always learn something new or get a good recommendation. In a couple of hours on the water, the conversation ranges from books, to writer friends, books, artist friends, history, sailmaker friends, films, family, books, seafood, etc..

In Norfolk, where he usually sails, these conversations are interrupted every few minutes by a barge or freighter trying to run us down. A few tense moments pass until we get out of danger’s way and can carry on. Here, no such problem. I catch Steve a couple of times realize he hasn’t looked up in a while, and reflexively snap up for quick look about. Makes me smile, because I know exactly what he’s looking for and why. By the end of the sail the lazy pace has settled in, and we realize we forgot to decide where we’re going.

Doesn’t matter, as long as it ends at the restaurant for a seafood dinner. Or more to the point, for three dozen oysters with some other food on the side. Oysters, like the waters where we sail, are ranked by their salt content. Sweet is nice, but salty is better.

 

 

 

It’s dusk by the time we finish. Steve then motored out to anchor across the water under a full moon. I didn’t have time to get camping gear together, so secured a room in a house across the river in Irvington.

 

 

 

 

 

 

 

 

 

 

Irvington, Virgina

 

 

 

Carter’s Creek, Irvington

 

Continue reading “Salient Saline”

Two Reefs Two Rivers ~ video

 

direct youtube link

 

Video from both days of sailing. We stayed up the Corrotoman the first day to stay clear of the wind and chop. Second day we headed out into the Rappahannock.

 

 

Double-reefed Off Parrott Island

 

Sunday is better. A little at first, then a lot. The Small Craft Warning is downgraded to an Advisory. It will remain gusty for the first half of the day, big gusts, but they will be spaced further and further apart as the day progresses, and lose their punch. By late  in the day it is as close to perfect as sailing gets.

Our hotel in Warsaw is not far from the one where Paul Manafort is spending a few nights before his trial, and not that unlike it, apparently. Warsaw had the closest available rooms we could find. Kind of weird for such a remote and unassuming place to be part of such a big story. There’s a Hardee’s and a McDonald’s, a Tractor Supply, beauty parlors, a tire store. A pressure treated wood factory. And, clearly, a regional jail.

It’s a 30 minute drive back to the marina. For such a small boat, a slip is only $25 for the night, with showers, a pool, a cafe. Well worth it. Next time we’ll just stay on the boat and skip the hotel and the driving. With the kinks from yesterday all worked out, and the boat already in the water and ready to go, we’re back onboard and underway with little fuss.

Continue reading “Double-reefed Off Parrott Island”

Double-reefed Off Yankee Point

photo by Doug Lawson

 

First sails for new boats are often troublesome affairs. Nothing has been tested or put under strain. Things go wrong. Little details left undone and  forgotten suddenly get remembered, always at inconvenient times. Knots come untied, screws come loose. It’s common enough that most builders take a “shakedown cruise” before the first official launch. Gives a chance for glitches to surface and get worked out under safe conditions, preferably without an audience.  So taking a new boat on its first real sail for two solid days, in a Small Craft Warning, is not a conservative move.

But that’s what we did.

Almost a  year has passed since Doug brought his new Marsh Cat back from the mountains of southwest Virgina.

Continue reading “Double-reefed Off Yankee Point”