From the Archives - Bits & Bobs Volume XXI

Introduction

This is the twenty-first installment in the “From the Archives – Bits & Bobs” series. Volume I of the series is here, Volume II is here, Volume III is here, Volume IV is here, Volume V is here, Volume VI is here, Volume VII is here, Volume XIII is here, Volume IX is here, Volume X is here, Volume XI is here, Volume XII is here, Volume XIII is here, Volume XIV is here, Volume XV is here, Volume XVI is here, Volume XVII is here, Volume XVIII is here, Volume XIX is here, and Volume XX is here. The different volumes are unrelated, though the real tales related are all real late and do all relate to me. You can read them in alphabetical order, numerical order, chronological order (note that these are all the same thing), check or money order, in some semblance of order, and/or because you’re “just following orders.”

What are albertnet Bits & Bobs? Well, imagine you’re making homemade pasta. When you cut the noodles, you get these stray shorter bits from the ragged edges of the dough sheets that fall on the floor or—if you’re smart—into a large bowl placed to catch them. You can totally use those fallen bits by gathering them up, pressing them together in a ball, rerolling them, and re-cutting them. That’s kind of what I do when I’m writing letters to friends and some extra words fall out of my word processor. The only difference is, I don’t reroll them, so what you are about to read is a big ball of scraps. Serve them with a nice Bolognese Ragu or Alfredo, or your favorite literary equivalent. (And if a presenting a big wad of literary scraps sounds half-assed to you, consider all the effort I put into that extended metaphor you’ve just enjoyed.) This week’s selections of Bits & Bobs are from letters I wrote during college.

[If you’re wondering whose portrait that is in the background, it’s the playwright Antonin Artaud, best known for his “theatre of cruelty.” I happen to remember this from 1990. Neither ChatGPT nor Copilot was able to identify him from the photo, by the way, thought Google nailed it instantly. To its credit, ChatGPT had a pithy comment: “Honestly, it might be the most fitting photo of someone who’s read Artaud and survived.”]

October 30, 1989

I had the weirdest dream last night. I’m at this party and dancing with this totally fly girl. I’ve never danced so well (and as you know full well, in real life I cannot dance at all) and we’re really hitting it off, and then the song ends and the girl collapses into my arms. First I think she’s trying to be funny but then I realize she can’t even stand up. Her legs drop out from under her, so I have to pick her up into my arms as though I’m going to carry her off. Then she whispers, “I have to tell you: I’m going to die. I’ve been poisoned.” I’m totally freaked out, looking at this girl’s face, and then she dies right then and there. I start to wonder if I’ve been poisoned too. I guess the Freudian analysis kind of conducts itself here…

March 1, 1990

I hope March goes better than February; that was out of hand. First off, I was sick all month. Then last weekend I finally started [collegiate bicycle road] racing [for the season]. The time trial sucked because I’m not fit and still not totally healthy after that virus. The criterium was one of these bullshit parking lot jobs that’s roped and coned off so they could make it twist around as much as they wanted. Half mile laps. Oil everywhere—in addition to all these big puddles of oil, the whole surface of the road had this kind of film on it. It was in Irvine, pollution capital of the universe, which gave me a gnarly sore throat. I figured on riding the crit mellow, for fitness etc. Well, the only guy on our team who was riding well was the new tri-guy, Eric, who hasn’t really perfected his sprint, so I went for the primes myself. I won one, and took third in another, and was actually kind of digging the technical course. I got in this breakaway of five halfway through, and T— and Eric were surely blocking for me, so I pretty much had to stick with it, but I almost didn’t want to because I felt like shit. On the other hand, Tony Palmer [a notoriously fast Colorado racer I’d admired as a junior, who raced in the Olympics in 1988], was in the break with me so I was excited about that.

Well, T— was sick and dropped out, and a then few riders bridged up including Eric, who of course would give the break a giant boost, almost guaranteeing our chances of staying off. So things were looking really good when suddenly I stacked in the hairpin for no apparent reason. I think I slipped on some oil. Ripped a big hole in my new Aussie bib shorts, and got this oily asphalt smear on my helmet—really sucked. Road rash on the hip, both arms, and the left leg, but not too bad. I ran over to the pit, and the asshole race officials wouldn’t give me a free lap because I didn’t go all the way around the course. So the Mavic neutral support guy just straightened my bars and sent me off. It took me like five laps to regain my composure, and I was dry-heaving and really wanted to drop out, but I was still in eighth or ninth or so, on my own between the peloton and the breakaway, so I chased hard and eventually got within about fifty feet of the break.

[Zoom in on that photo and you can see the oil smear on my helmet. Note also my teammate, T—, watching from the sidelines.]

I thought I was about to latch on when Eric attacked and blew the break apart (temporarily, anyway). So much for closing that gap. I thought maybe I could solo in ahead of the main pack but about ten laps later I got swallowed up. Towards the end of the race the break lapped the field and I was trying to get Eric off the front, since I knew that was his best chance at winning. Well, Tony Palmer was having none of that, and started cussing at me and yelling, “Don’t even try it!” Somehow, in the moment, feeling as crappy as I did, I accepted his authority, sat up, and just waited for the sprint. Damn, the tricks your mind plays on you when you’re miserable…

March 16, 1990

I was going to hit the sack but I forgot I did my laundry this afternoon and left everything festering in the washer so I just went and put it in the dryer and now I have to kill some time while it dries and I don’t really feel like studying even though I really should because finals start next Monday and I hardly even have a clue what’s going on in any of my classes, especially this boring as hell history class which is so lame that the best I could do for notes are statements like “1629: some emperor on verge of something with his edict of restitution which means something is restored to church; things after this began to go downhill for the Hapsbergs while Wollenstein is an example of why whatever war this was was the way it was, however that was” (that’s an actual quote from my notebook) which doesn’t really put me in a very good way as far as the final exam goes.

May 28, 1991

My dickhead roommate—the one with the Rolex and the $15,000 stereo—had a birthday recently. His mom called and asked for him, and when I said he wasn’t home, she said, “Just tell him happy birthday, and that his present is in the bank.” Nice. Meanwhile his girlfriend got him a Nintendo and he plays it 24x7. At first I couldn’t figure out why she bought him this thing, and then I realized, duh, she’s sick of him, and this will get him out of her hair. Easy enough for her … she doesn’t have to live with the guy. First thing in the morning, he’s playing “Contra,” and actually, he never stops, except to go to the bathroom or grab a snack. Same game, day in and day out. My other two roommates and I keep telling him to get a life and his answer is the same as when we tell him to do his dishes: “I’ll do it later.” What really sucks is that every time his guy is killed, he cusses like a sailor. Like it really matters. What’s he supposed to say if, one day, the television—my giant 26” Sony Trinitron Color Console in the giant cabinet—falls on him and pins him to the floor? Nobody will answer his call for help because we’ll assume his little Nintendo guy just got shot again. I keep hoping he’ll finally lose his temper and smash my TV so I can make him buy me a new one that isn’t all blurry.

November 25, 1991

So I’m in the school library restroom and this guy comes in, heads to the next urinal over, and before even doing his business flushes it. I wouldn’t have noticed except he used his foot, so for a second it looked like he was trying to kick me in the head. I have no problem with him flushing with his foot since the handle is presumably gross, but why the pre-flush? I guess he doesn’t want his good, clean urine mixing with the bad, dirty urine in the bowl. That would be terrible, even if he’s not planning to use that urine again. Just the very sight of his elite urine mixing with the vulgar, common urine is too harrowing for him to witness. What a knob.

April 20, 1992

My mom and [her husband] the Landlo’ left their car here while vacationing in Morocco and I’m using it as much as possible to date this girl. So far that’s only been twice, so I better hurry things up while I still have the car. I don’t expect you’ll chastise me for refusing to have a really deep introspective contemplative period following the death of my last romance; as you well know, I am not some sort of Love Guru. But I can hold my own with the women: which is good, because that’s what they usually want me to do.

July 29, 1992

[To Giro Sport Design, Inc. who had given me a free helmet about six weeks before.] Dear Giro people: A month ago, my Giro Air Attack acted as liaison between my head and the ground. I was mountain biking in nearby Tilden Park, and that’s about all I remember because for several hours after my accident I alternated between being unconscious and incoherent. I was flown by helicopter to the nearest trauma center, where I underwent a CAT scan and was stitched up. Twenty or so sutures were put in my forehead beginning, notably, just below where the helmet left off covering my forehead. I have suffered no permanent damage to my head and for this I thank you.

October 8, 1992

I called my dad the other day and said, “Dad, I need twenty dollars.” He said, “Fifteen dollars?! What do you need ten dollars for?! Okay, I’ll mail you the damn five dollars.” But he didn’t.

But seriously, my medical bills are starting to catch up with me after that mountain bike crash. I wrote letters to the ambulance and helicopter companies, saying basically, “I have no money. Please dismiss my account. Thank you.” The helicopter company was cool about it, but the ambulance company ($550 to drive me one block, to where the helicopter had landed) wrote back threatening to slash my credit rating if I didn’t pay up the balance. (My crappy school insurance had only paid $100.) So now I’m on the installment plan, sending $50 a month through next June for a five minute trip I don’t remember going on. I plan to write in the “memo” section of each check, “You thieving bastards!” or at least “You teething hamsters!”

—~—~—~—~—~—~—~—~—
Email me here. For a complete index of albertnet posts, click here.

Biking the White Rim Canyonlands Trail With Young Bucks

Introduction

Every year or so I get together with my friend Peter to do a monstrously difficult bike ride. This year would have been in celebration of forty years of friendship, except that neither of us actually noticed this milestone at the time. (I did just now.) Just to mix things up, we brought along Pete’s son H— and two of H—’s friends from the Colorado State University cross-country running team. This is a little bit like inviting Godzilla to your garden tea party with his pals  Megalon and King Kong, expecting them to sip daintily and take just a few cucumber sandwiches instead of trampling everything. If you like the idea of me suffering, well, read all about it right here.

This was a one-day assault on the Canyonlands White Rim Trail, which Strava says most riders complete in two to four days. Pete had done it in three days with H— a couple years back, and this spring H— decided it would be a pretty good idea to hammer it out in one. (So honestly, it was me being brought along as an afterthought.)

Executive summary

As I’ve mentioned before in these pages, I’m not a big astronomy fan. The old cliché about staring up at the stars and saying, “Kinda makes you feel insignificant, doesn’t it?” doesn’t seem that profound to me, because all kinds of things make me feel insignificant (like being middle-aged, and an empty nester, for starters). I don’t need to travel to some remote place where there’s no light pollution just so I can feel like a trivial little speck.

Meanwhile, I learned through this exercise that if you travel to a sufficiently isolated place—in this case Canyonlands National Park near Moab, Utah—you can be so dwarfed by giant reddish rock formations towering above you that you never need to see the celestial heavens again, if feeling insignificant is your thing. In the photo above, look how Peter (the farther-away dude, in black) is so diminutive compared to the rock wall next to him. (If you can’t even make him out, click the photo to enlarge, which goes for all the pictures in this post.)

And yet, this being by far the longest mountain bike ride of my life, I feel like my Man vs. Nature battle didn’t come out so very badly. Despite a protracted ordeal in an unforgiving landscape, I find myself “still alive and bitching” (to quote the philosopher king Marshall Mathers). You might be alarmed to know we were out for almost 11 hours with virtually no shade but I barely noticed … we had far bigger difficulties to surmount than that. For example: the CSU brat pack; the relentless pounding of our tires over unforgiving landscape; and the formidable Shafer climb (starting at mile 75). If all you care about is the fact of us pulling this off, congratulations, this Executive Summary is all you need, and you can click here for dessert. Otherwise, read on for the gory details!

Short version

Dinner the night before, at our AirBRB (a nickname I’ve just coined, I think), was De Cecco pasta with trailer-trash sauce. This sauce is made by sizzling some crumbly house-brand Italian sausage in a pan, glugging some jarred sauce in there, and heating it up. Since I drove like a thousand miles for this get-together, I splurged on some weirdly high-end sauce that’s like $10/jar. (Did I pay that? Of course not. I had a digital coupon or something.)

I slept poorly the night before because a) I’d eaten way too much pasta, and b) during the two-day drive out to Moab I adopted an all-taqueria-all-the-time approach to dining, so I had percussive flatulence all night, loud enough to wake myself up (and probably some of the 100 or so species of arthropods we can presume were sharing my room, if this dwelling was typical). Did I regret all that Mexican food? No. Not even considering the long hair I found in one of my burritos, which was from a forlorn taco truck in the middle of a giant dirt lot in a remote part of Provo. I kept pulling on that hair and it just kept coming, like a magic trick. And yes, I did finish that burrito. Think of how many hairs are discovered and removed just before restaurant food is served, or hairs that we actually ate, unawares, because we were eating too fast. (Or is that just me?)

My breakfast on ride day was a seriously overripe banana (peel almost black) with peanut butter, and coffee blacker than the banana peel. The AirBRB had a coffeemaker, but they’d stocked the wrong size filters, so it’s a good thing I brought my own pour-over cone and filters from home (along with my standard-issue ground Peets). These items had saved me at the motel the morning before as well, where the only teabag-style “coffee” they provided for their stupid coffeemaker was decaf. I’m strongly considering bringing ground coffee, my cone, and filters with me every time I leave the house from now on.

During the ride I ate an untold number of Clif and Kind bars, washed down with about nine  or ten bottles of water. Knowing the precise number of bars wouldn’t properly document the actual caloric intake, because there’s a lot of chocolate in a Kind bar, most of which melted due to the desert conditions and couldn’t be extricated from the wrapper. I felt kind of foolish eating these bars because all of my riding pals ate almost nothing but peanut butter and jelly sandwiches. I really need to get in on that.

By the time we finished the ride, showered, limped back out to the cars, and drove into Moab for dinner, not much was open. We hit the Moab Grill which was still hopping. I knew as soon as we sat down that a) I wanted wings, real bad, and b) Pete would refuse to have anything to do with them. He’s above wings, apparently. We’ve argued bitterly over it in the past, sometimes after brutal bike rides such as this, and never order them. (It’s not that I couldn’t eat a whole plate of them by myself with no appreciable dent in my appetite; it’s that they’re meant to be shared. Solo winging would be like drinking alone.)

Of course we had the three young bucks at the table, but what if H— took after his old man with the buzzkill no-wings-ever policy? And what if the other two dudes, G— and T—, were, like, vegans or something? You never know with elite athletes. So I tentatively asked, “Would anyone be into getting an order of wings?” G— grinned and said, “That’s practically all I’ve thought about for the last two hours.” Score! God, those wings were good. Buffalo style, with ranch, of course. I miss them. I just love how you can shove an entire wing in your mouth and then zip the bones out in one motion, leaving all the delicious meat to be exuberantly chomped. I also had a Reuben that was pretty darn tasty, on marbled rye that the waiter specifically recommended, with hella fries dragged through mayonnaise. I also inherited like half of H—’s “Dyablo” burger (jack, bacon, jalapeños, roasted red peppers, hot sauce) that was super good despite the misspelling. I don’t know what is wrong with that kid that he doesn’t even finish his burger after a 105-mile mountain bike ride, but at least he likes wings. And it’s not like I’m complaining about the secondhand food.

The really messed up thing is that I’d brought a four-pack of Fieldwork IPA all the way from California to drink with Pete après-bike (or should I say après-vélo?), but we were so shattered from the ride, we just didn’t feel like drinking. And we didn’t. Okay … now are you getting a sense of how hard this ride was?

Long version

This long version is truly long, even for an albertnet post. What can I say? It was a long ride. If you think reading this is hard, go try riding White Rim sometime.

You may have noticed from the map above that there’s almost nothing on it but the crenulations representing topography, and one little actual paved road, that being Country Road 143 that we were on for a few miles. No towns, no trailheads, no warming huts, no bailout roads to civilization. Granted, if the map were more complete it would show the little visitor’s station we stopped at, ~80 miles into the ride. Other than that there was just nothing and almost nobody. But we had each other.

Wait, did I just imply that having each other was a good thing? Honestly, endeavoring to keep up with three NCAA Division I cross-country runners is one of the dumber things I’ve ever done. Yeah, sure, they were on bikes, which is more Pete’s and my thing, but then, fitness is fitness, and youth is youth. Plus, they had their inevitable rivalry, leading to irrationally exuberant accelerations. For the first 40 miles, it was more or less a death march hanging on for dear life behind them. It wasn’t just hard physically (I mean, duh) but psychologically too … I kept thinking, wait, we’re only 20 miles in  and the temperature is climbing and I’m already suffering and shouldn’t I be saving some energy for later, and specifically for that monster climb, instead of accepting this breakneck pace? I didn’t realize until I looked at the bike computer data afterward that these first 40 miles were almost all uphill. That’s because everything is so wide open, you can’t get a sense for gentle gradients. I just thought it was the rough terrain and the pace that were making it so hard.

Obviously it’s only the shallow climbing that’s invisible. It’s pretty hard to miss a steeper climb like this one:

That’s the Green River in the background there, BTW.

Climbing on a road bike, on asphalt, is hard enough, but at least that’s just a matter of turning the pedals. On a really rough trail—and I was surprised how legit and rocky and complicated a lot of this trail was, compared to the dirt road I’d naïvely imagined—you also need to steer around the bigger rocks, bumps, etc. because at such low speed, they can stop you cold. Sometimes you can’t avoid an obstacle and have to use body English to pop your bike over it, one wheel at a time. Meanwhile, the whole time you have to lean really far over the front wheel or else it’ll lift up off the ground (even if only slightly) at which point you lose the steering and your brain shuts the whole operation down so you unclip from the pedals and are dead stopped. Riding with your weight this far forward, you have barely enough traction on the rear tire, so it slips from time to time, costing you priceless forward momentum. Add in that you don’t know how long the climb goes on, and it’s hard to have faith you can make it to the top.

Sometimes we did give up and walk our bikes, which was a major letdown. For example, check out the pitch shown below, coming at the end of a prolonged section of brutally tough climbing. Pete almost made it. I was maybe 2/3 of the way before realizing (or at least imagining) that if I waited until the even steeper bit ahead to bail out, my shoes might slide out from under me. Pro tip: as you start to walk your bike, grab the rear brake to lock that wheel, or the bike will drag you backwards down the slope.

By the way, the shade you see in  the above pic is almost all we got the whole day.

We started getting some nice downhills. I don’t mean the super-steep technical ones where you’re hanging your ass over the rear wheel to keep from face-planting (though we did get those too, and they were glorious) but the more relaxing easy ones where all you have to do is steer around the larger rocks (because who wants a flat tire or other mechanical out in the middle of nowhere?). Unfortunately it’s really hard to take photos or make movies while doing these, but one of the young bucks somehow managed:

It was bumpy enough that I lost five bottles, only four of which I managed to retrieve. Three losses were from the side pockets of my CamelBak. I didn’t use the bladder with it, because I needed room for tools, the first aid kit, food, and five water bottles. (If you’re interested in everything a seasoned mountain biker has in his pack, click here.)

The trickiest part of these downhills was that you’d occasionally hit soft sand, which can sometimes seem to grab your wheel and twist it, so your bike starts to jackknife. Gave me the heebie-jeebies every time.

We stopped for rests periodically, especially in the more scenic places like this chasm we peered into.

Here is our lunch stop. (This happened to be around 1 p.m. but really, every food stop was lunch. It’s like when you’re in the grocery store checkout at like 4 p.m. and the manager says to your cashier, “Go take your lunch now.”) Look at H— peering at his PBJ. He’s probably thinking, “Come ‘ere, you.”

At around the southeastern-most point of the loop, at say 5 o’clock (i.e., the position of a hypothetical minute hand on a clock, not the actual time), several of our phones chirped because we randomly had a cell signal for the first time all day. We stopped and fired off some emails, because after all this was a workday. Kidding! But I did snap the below photo and texted it to my brother, and he actually got it!

By the time I tried to send the same pic to my daughter, the signal had evaporated. Probably it had been bounced off a passing jet, maybe even a spy plane, and was a flash in the pan.

I was about to type a thousand words about how majestic and architectural the landscape was, but instead here’s another photo.

If you’ve ever wondered how these formations got to be how they are, and especially if you’re a female reader, let me explain (or mansplain) it all from a geologic perspective. Wait! Come back! I was kidding! I have no idea how this land got to be this way. I’ve had it explained to me half a dozen times over the decades but I never listened. It’s complicated. Something about sedimentary, igneous (or is it Ignatius?) deposits, once submerged by an ancient ocean, or was it crushed by a glacier? I actually have no idea.

You might be wondering: does Canyonlands have anything to compete with the amazing pupfish of Death Valley? Well, not that I saw, but there were occasionally these darling little cactus flowers. (Bike tire included for scale.)

I count at least two or three species of insect in there. It’s like a big bug party in the desert!

While we were stopped for that photo and some chow, an SUV rumbled slowly by. A puffy middle-aged woman was in the front passenger seat and gave us a bored glance. She was wearing one of those ring-shaped neck pillows people use on long airline flights. Perhaps she was just doing this drive for the commemorative bumper sticker and couldn’t wait for it to be over (though that’s exactly what she was doing).

At around mile 60, an inventory of pain had assembled itself in my brain and my inner voice was whining. My back hurt (mainly from the strain of climbing). My right collarbone hurt where the strap of the (overloaded) CamelBak was pressing down, because of the heads of the screws holding the plate in there that fixed my once-broken collarbone. All my toes felt broken, which tends to happen on really long rides (despite my excellent footwear). Perhaps most of all, my hands hurt from my bike’s continuous impacts with rocks and hard-edged slabs we kept bumping up on and down off of. I’d brought long-finger cycling gloves and short-finger ones, the former without padding and the latter with gel, and ultimately opted for the long-finger. I don’t know what I was thinking … they’re just what I normally wear mountain biking, for protection against poison oak. But was I going to find that here? (I can sense you shaking your head.) I couldn’t switch to the padded gloves because G— had forgotten his gloves and was thrilled I had a spare pair. Would it be a dick move to demand that he trade with me now? Yeah, it would, dang it. So my palms were really raw. Have you ever gotten a little overexcited while tenderizing a pork chop, working out some demons perhaps, and you realize the meat has become so roughed up and soft it’s almost like moss? That’s how I imagined my hands had become.

Eventually we made it to the base of the dreaded Shafer climb. G— and H— took off ahead, ostensibly to make it to the ranger station before it closed. We didn’t actually know its hours, and it was already 4:30 p.m. with zero chance of getting there before 5 anyway, but the young bucks were out of water and thus desperate. Here’s Pete looking back at me as if to say, “Okay, they’ve got enough of a head start. I’m going hunting … see you at the summit.” The look I returned, as I snapped this photo, said, “Release the hounds!”

(Full disclosure: Pete’s look back surely meant nothing of the kind, nor did my return glance. I’m adding these subtexts only now, to give this report some drama and the shimmer of fiction.)

In the photo above, if you look straight up from the top of Pete’s head (zoom in!), you can see the switchbacks we would have to face.

Pete’s chase was swift and ruthless. The climb was ruthless but not swift, not for me. This next photo is from two minutes later. Not only has Pete caught H— but look how far ahead he is of me! I think I even used my camera’s zoom for this shot!

I rode my own pace, having released myself off the back on my own recognizance as I so often do. I know better than to try to run with the bulls. Here’s a little video documentary I made.

If you pause video that near the beginning to look at my bike computer readout, you’ll note I was going only 4 mph. Go ahead, mock me … but also consider the grade was 14%. (See what I mean about the wide open topography making the grade look shallower?)

Almost twenty years ago, my wife and I did a mountain bike vacation in Moab and, for shits and giggles, took a sunset river cruise narrated by a quasi-historian. The script he read from was cheesier than all-you-can-eat fondue. Our favorite line, delivered toward the end after a long pause (calculated to build suspense, I suppose), was, “And now, in the darkness of night, we ponder the legacy that is ours.” So pompous, and so meaningless! My wife and I like to trot out that utterance from time to time. And perhaps pondering our legacy is what G— was doing when I came around a bend to see him stopped.

Or maybe he was just enjoying the shade and taking a breather. I’d kind of been counting on these runners to eventually tire so they’d ease up on us. I’d asked beforehand how long their longest event is; it’s the 10K which takes them like half an hour. Obviously their training runs are longer, but then nobody runs for eight or nine hours at a stretch … and yet this kind of duration is typical for Pete and me on our monster rides. (Our 2022 slogfest took 8:37:47 and our 2023 gravel adventure took 8:37:32.) H— , T—, and G— are like greyhounds, whereas I’m more like a lobster lumbering across the ocean floor. As I distance cyclist I am kind of made for this, or more to the point I kind of made myself for this. We’d only ridden for six or so hours; I was just starting to find my groove.

I could still see Pete and H—, utterly dwarfed by the canyon wall.

The landscape was so literally awesome, so  sublime, that I kept trying—but always in vain—to  capture its grandeur with my phone camera. Perhaps my best effort is this accidental video, that was supposed to be a still photo. Though it’s obviously pretty sloppy camerawork, I think it captures the feeling of this climb better than any of my stills.

Switchback after switchback, the climb went on and on. Obviously I was suffering hugely, but at least the trail was smooth here and I settled in to a rhythm of sorts. If you read my posts from my epic French Alps cycling “vacation,” you’ll understand my point when I say this kind of suffering is the devil I know. (If you missed that series, cancel all your meetings and click here.) I felt like I could pedal like this all day, and probably would. At least it was easy to appreciate the progress I’d made, as shown by this photo. (SUV and T—, or maybe it’s G—, included for scale.)

Just before the summit of the climb, I caught Peter and H—. (The only explanation for this is that H— was hurting and had slowed down, and Peter hung back for some quality father/son time, to witness the lad’s suffering.) At the top, H— wobbled off the trail, set down his bike, and lay down on the ground to rest. Pete and I rode a couple miles to the Visitor’s Center to see about water. It was closed but had a spigot and we filled all our bottles. Bringing them back to the young bucks gave me a welcome paternal feeling, and I reconsidered my earlier plan to file charges of Elder Abuse against them.

We woke up H—, topped up everyone’s bottles, and set back out for what we thought would be a 20-mile descent, the first five miles or so being on actual asphalt. Instead it was rolling (if mostly downhill). That might not sound too bad, but each time the road tipped upward, it was like a slap in the face. Our group broke apart and regrouped a few times and over the last few miles I did some quality wheel-sucking behind T—, who’d caught a second wind at like mile 95. At one point I actually hallucinated and thought I saw buildings, like a small town, in the distance, indicating that we’d made a horrible navigational error and were screwed. “Do you see those buildings down there?” I asked T—. He looked at me as though I were crazy, which I suppose in the moment I almost was.

Eventually we reached the cars, our ride actually done, and busted out the cooler. There were only three Cokes, which were snapped up by the lads, but Pete and I were happy to make do with beers. Here is our official post-ride Beck’st:

Fortunately Mother Nature had put out some nice furniture to relax on. I love how, in this final photo, H— appears to be deep in thought, doubtless pondering his life choices and how he ended up here.

I can’t wait to return next year. With an SUV. And a neck pillow.

Stats

• 105.1 miles
• 8:44:05 ride time
• 12 mph average speed (really not bad for mountain biking…)
• 7,283 feet cumulative elevation gain (based on Pete’s Strava, presumably more accurate than the bike computer value shown above)
• 6,207 feet maximum elevation
• 120 bpm average heart rate
• 157 bpm max heart rate
• 4,316 kilocalories burned

—~—~—~—~—~—~—~—~—
Email me here. For a complete index of albertnet posts, click here.

How to Achieve Inbox Zero

Introduction

In last week’s post I made the case for Inbox Zero: that is, for being so on top of your email that your inbox is virtually empty (say, a dozen or fewer emails). To recap, Inbox Zero is about being more effective with email, meaning you’ll possibly read less of it, definitely re-read much less of it, and stop missing important emails because they were buried under all the unimportant ones. The goal is to make better use of our time, so that we spend less of it doing email. In this post, I am going to explain exactly how to achieve and maintain Inbox Zero, based on how I’ve managed it for the last several years.

[A note on the art above: a concerned reader was aghast at my use of A.I. to create the art for last week’s post. She was so keen to keep it real, she created this original art just for me—and you.]

One prerequisite

There is an important prerequisite to achieving Inbox Zero, at least the way I do it: you have to use Gmail as your email interface. This doesn’t mean you have to use a Gmail account. (More on this later.) Now, I’m not some major Google fanboy, and they didn’t sponsor or promote this post (or this blog) in any way. Google makes its money through ads, and I’m not big on advertising. I also don’t appreciate how their YouTube algorithm tried to addict me to sexy yoga videos. Moreover, I bristled at the original Gmail because the consumer version, when it came out, had ads that were generated based on its bot reading the email message content. This so unnerved me, I created a technique to stymie it. But Google eventually ditched the ads, probably after reading this blog and realizing I was right. (Yes, that was a joke.) But now I’m sold on Gmail.

When my employer switched to Google Workspace, and Gmail became a part of my daily life, I realized not only that its conversation view is much more efficient, but that the use of labels instead of folders makes all kinds of sense. In fact, labels are the key to maintaining Inbox Zero. So if you’re still committed to using Outlook, this post isn’t going to be of much help.

If you don’t use Gmail, don’t stop reading! If you’re not among the 76% of Americans who use Gmail for their personal email, you can still keep your Yahoo or Hotmail account, and set up the Gmail interface (both on your laptop and your Android app) to pull in email from either (or both) of those platforms. The Gmail interface works great for my personal email (which is on my own domain, via the Yahoo/Turbify platform), along with my Gmail, of course. It’s nice to get everything in one place.

(I’m not going to explain how to port your Yahoo or Hotmail over to Gmail … that kind of task is what ChatGPT is for. It did a great job guiding me through the process. When one of its instructions doesn’t work—which will happen, as these interfaces undergo minor changes all the time—ChatGPT can course-correct very well. In fact, if you told ChatGPT, “I am having trouble with the POP3 settings because my neighbor is having a huge party and they’re making too much noise,” GPT will help by asking, “Would you like me to draft a speech or brief note that you can present to ask them to quiet down?” And if upon reading this draft you respond, “The note needs to be shorter and more emphatic because I want to write it in Sharpie on my husband’s bare chest,” GPT will accommodate that request as well. So, you may now wonder, why wouldn’t you just ask ChatGPT how to get to Inbox Zero? The answer is, because it’s only really good at rote technical configurations, not at strategy. Yet.)

My Inbox Zero strategy

As with all techniques for everything, there are five steps to reaching and maintaining Inbox Zero. No, this methodology won’t get you to where you literally have zero emails in your inbox, but when you start doing start-of-day triage and some catch-up throughout the day, you’ll get to where most of the time you’ll have relatively few. The crucial thing is to have no more  in your inbox than Gmail’s first page can display. The default is 50 threads. Anything that doesn’t fit on this first page is guaranteed to be neglected, because the chances of you ever seeing it are negligible. (Sure, you could find those emails with the search feature, but how will you know to search if you don’t know the email exists? Do you routinely search on “invoice past due”? Or are you waiting for someone to say, “What? You didn’t see my email?” so you can search on their address?)

With no further ado, here are the steps.

Step #1 – Create a few filters and a couple of new labels

This step is mainly necessary for your work email, and is optional if you work for a small business. But if you work for a large corporation, you surely get a ton of email that’s broadcast daily from HR, your marketing department, news feeds, vendors, and various other non-personal sources. You are generally not expected to respond to these emails, so they should definitely be considered lower priority. They shouldn’t compete for precious visible-inbox real estate with any email that a human took some trouble writing.

Thus, you should create filters that target the daily all-hands update emails and filter them out such that they don’t even hit your inbox. Since these messages are not as useless as direct marketing solicitations, you’ll want to also label them (automatically!) in case you need to find them later. Figure out how many labels you need: you might have a “Corp updates” label and another for “Industry news,” or you might just have a catch-all for “Bulletins etc.” Now, I know filtering out emails so they never hit your inbox can seem scary, but bear in mind two things. One, if you haven’t been doing Inbox Zero, lot of emails have always been invisible to you anyway, by being buried among others and/or not on the first page of your inbox. Two, you can always peek at the mass of unfiltered emails by clicking the “All Mail” link down the left of your screen:

(If you don’t see this “All Mail” link it’s because Gmail has hidden it; click the “More” link to expose it. In the snapshot at left, the view is expanded so there’s a “Less” link; that’s where the “More” link would be shown if this view were collapsed.)

For your personal email, the first filter should get rid of unasked-for solicitations like the daily email you get from Speedo because you once bought that bathing suit from them (you know, the one that didn’t even fit so you returned it). Filter out all these quasi-spammers—the companies you did choose to do business with who are now like remoras. (Myself, I have a Hotmail account that I use for all e-commerce so I can more easily ignore that spam. If I need to file a receipt I log into the Hotmail, find it, and forward it to my personal email. Otherwise I ignore Hotmail entirely; it’s at Inbox 48,376.)

With these various filters in place, at least you’ve somewhat mitigated the fusillade of daily emails, hopefully reducing it to under fifty so that facing your Inbox for daily triage will be less daunting.

Next, if this is your work email, create a label that is your boss’s name, and set up a filter that applies this label to each of this person’s emails to you—without removing the email from your Inbox. Make this a bold, perhaps red label. If you’re lucky and your boss is named Aaron, this label will automatically show up at the top of your list of labels (which is also your list of folders … more on this later). If your boss’s name isn’t Aaron, put an underscore character at the beginning to move it up. Going forward, instead of starting your workday by perusing your inbox, you can start in your “Boss” folder (or, if your emails don’t pile up too fast, you can still start in the inbox and just look for that bright red label.) The idea here is that the very first emails you should read are the ones from the person who has direct influence on your salary. In the below example, the person’s boss is named Zoe, so two underscore characters are required.

You’ll also want to create a label called “_Follow-up.” Make this a bright color, too. The underscore character before the “F” is to move this label to(ward) the top of the list. The “_Follow-up” label is important for both your work and personal email … more on this later.

Does it make sense to automatically flag emails from your spouse, the way you did with your boss? Perhaps, but only if you get a lot of email from him or her. (Mine just yells across the house, like me.)

Again, ChatGPT can walk you through how to set up the actual filters and create and color-code the labels. All kinds of helpful people have already documented this process in various forums etc., so ChatGPT can research and distill that process for you.

Step #2: Clean slate

Obviously if you’re currently buried in thousands of emails after years of neglect, you’ll need to start with something other than mere triage … it’s a little late for that. To achieve a clean slate, take a deep breath and ask yourself what the odds are that you’re really going to ever read emails 51 through 25,359 in your inbox. Once you have accepted that the answer is “hell no,” you need to just archive them all, in one fell swoop. First navigate to your inbox. Then find the little checkbox just below the “Search mail” field at the top of the Gmail interface. If you hover your cursor over it, a tool-tip will appear that says “Select.” Check that box to select the first 50 emails, or better yet, accept the offer to select all 25,359 of them (i.e., however many you have total). Then click the icon next to the checkbox that looks like a folder with a down-arrow on it, as shown below. This will archive all selected messages, which means they’ll no longer be in your inbox. Where do they go? Into the ether. Probably the same place electricity goes when you turn out the light. They’re still on the mail server, though, and you can still see them by selecting “All Mail” as described above. But you don’t need to see them. They’re dead to you. Get on with your life.

[A note on the screenshots in this post: some are a bit hard to read. Click on a picture to enlarge it.]

The only problem with that mass archival is that nothing is labeled, so it’ll be hard to find past emails. That’s the consequence of waiting this long to get organized. Proper implementation of Inbox Zero means being organized going forward, not just clutter-free. Thus, once you have zero emails in your inbox (or maybe half a dozen new emails since they continuously pop up out of nowhere), you need to do regular triage on all the new stuff.

Step #3: Triage and pre-labeling

Okay, let’s assume you now have a clean slate and an inbox that doesn’t represent years of neglect. When you open Gmail first thing in the morning, you’ll likely still see dozens of emails, and you’ll start to panic, but don’t. Just follow these rules in making your way through the pile.

Start with the boss. Remember that new filter you created that automatically labels emails from your boss? Read those first. (If this is your personal email, and you created a rule to automatically flag messages from, say, your kid who’s a terrified college freshman, start with those.)

Jettison spam. If you see spam or quasi-spam messages, delete them on sight. You can go down the list of threads selecting all the chaff via the checkbox, then click the garbage can icon on your toolbar. This is incredibly satisfying. If you’re seeing a lot of spam from a single source, create a filter to kill it off forever. (Zap Zappos! See ya later, Speedo!)

(I had to cheat with the snapshot above … that’s a view of the Promotions tab, where Gmail automatically moves the quasi-spam solicitations. If you don’t see inbox tabs like Promotions, Social, and Updates, enable them in Settings/Categories.)

Scan for important messages first. Scan through the subject lines for anything that looks important, like one from a friend you’re making plans with, or a work colleague you’re knee-deep in a project with, or a thread you’ve been working that has new activity, and open that first. Scanning never worked before, because you had too many emails. Now it’s actually a reasonable way to triage.

Pre-label your threads. For every email you open, all you’re doing right now is skimming it to judge its level of importance, and—crucially—labeling it. This is the most important rule: don’t wait until later to “file” it. Label it now, and it’ll kind of almost be filed already. (More on the “why” of this in a minute.) Note that you’re not moving this using the very obvious button on the tool bar (i.e., the one shown below). That will remove the thread from your inbox. You want to label it while leaving it in the inbox, for this triage phase.

Instead of clicking “Move,” click on the three-dot “kabob” icon (if you hover over it, a tooltip will tell you it’s the “More” icon) and select “Label as” from the drop-down menu. It’ll show you a list of all your labels, and you can either just scroll down and find the right label, or you can start typing the name of a label and it’ll zip right to it. Click on the label name, if you’re only applying one label, and you’re done.

You won’t need to bother with the kebab menu if you switch to the advanced toolbar. Here’s how to switch:

Then you’ll have a dedicated button to apply a label without moving the thread:

The great thing about labels in Gmail, vs. folders in platforms like Outlook, is that you can apply more than one label to an email thread. That way, it’ll show up in multiple folders. Well, not folders exactly … that’s the confusing thing about labels in Gmail. Yes, they label message threads, but they also act like folders. (Kind of like how light is both a particle and a wave.) When it comes to classifying a thread, you’re applying labels. But labels act like folders when you’re at the main Gmail screen and want to navigate your threads. It’s like your threads can be in two or more folders at once.

Let me give you an example. Several of my friends and family members like beer as much as I do. We send each other Beck’sts, which are beer-themed emails (click here for details). Often one Beck’st begets another, and we have stirring dialogues not just about our beers, but about other topics like being middle-aged, being a parent, etc. (Oddly, a fair bit of my modern correspondence begins with a Beck’st.) Since these threads aren’t just about beer, but also about friends and family, I want to label them accordingly. So I select “Label as” from the drop-down, and check boxes next to all the appropriate labels:

When I’m done, the thread will have all the labels it needs. This means I can hunt for it in my brother B—’s folder, or my friend D—’s folder, etc. If I remember, for example, that D— wrote me about becoming a grandpa, I can search on “grandpa” in his folder whether or not I remember (years from now) that he announced this via a Beck’st.

(Sometimes, you’ll have labeled and archived—i.e., filed—a thread only to receive a new response to it, perhaps from someone on the distro who hadn’t chimed in before. The thread will show up in the Inbox again, at which point you can add the new correspondent’s label to it.)

Remember, you don’t maintain Inbox Zero by taking action on every email right away—you’re just labeling it during triage when this is so easy to do. Triage consists of figuring out whom the email is from, and what it’s about (if you bother to file/label emails by topic). You’re labeling it now, so you never have to revisit it again. Then you can actually get some work done, knowing the most important emails have at least been read and you know what’s waiting for action. Disorganization is distracting!

Again, the pre-labeling is the game-changer … if you try to file emails later, you’ll waste gobs of time re-reading each thread to try to remember what it’s about. Label it the first time you see it, as this will only take seconds. Then, filing later is just a matter of jettisoning it from your inbox.

Flag for follow-up.  If an email will obviously require a reply or some other action, don’t just label it by sender and/or topic—also apply the “_Follow-up” label you created in step #1. Some email is just information, and some needs action. This is the best way to differentiate. Also, by selecting the “_Follow-up” label/folder, you’re basically creating a to-do list of emails requiring action. 

To add to my exhortation to pre-label, the key difference between an email folder (like Outlook uses) and the labels that Gmail uses is that a label doesn’t, by itself, move the email. It just gives it an identity that will persist forever (unless you decide to un-label it). A labeled email is breathtakingly close to being a filed email … all you have to do is get it out of the inbox (by archiving it, or removing the “Inbox” label, which amount to the same thing).

Step #4: Archive messages

Once you’ve read or at least scanned all the emails in your inbox, it’s time to tackle the ones you labeled “_Follow-up.” Since this (probably) won’t be that many threads, you can see them all at once (perhaps by clicking the “_Follow-up” folder, or just eyeballing them in the non-overrun inbox), and decide which are the highest priority. Once they’re dealt with, you can remove the “_Follow-up” label and archive them. If there are emails remaining in your inbox, perhaps a few of them should stay there (to be visible for a while, even if they don’t require action) but others can be archived right away, and all of them eventually. (There’s really no point leaving them in your inbox forever, especially when they’re already labeled.)

There are two ways to archive (i.e., file) email threads: the Archive button, and removing the “Inbox” label. Here’s how you’d archive via the button:

Or, you can click the little “x” on the “Inbox” label; now this message will no longer appear in the inbox.

This second method has the benefit of being applicable across labels. For example, it’s how you’d remove the “_Follow-up” label after action is taken. So when you think your inbox is getting out of hand, you can start at the bottom and work your way up, deciding when it’s time to click the “x” next to the “Inbox” and/or “_Follow-up” labels as appropriate. When you’re done, not only will you be closer to Inbox Zero, but you’ll have made great progress in your filing. If you get behind on that, but realize 20 of your emails are no longer timely, you can just check them all and click Archive. Since they already had labels, they’re now correctly filed, and you didn’t have to reopen them!

A final note on labels: I recommend that, upon sending an email that is not a response (i.e., starting a new thread), you go into your Sent items and slap a label on the message. For example, when I send a Beck’st, I’ll label it, so that even if nobody responds it’ll still show up in my Beck’st folder. And if somebody does respond, his response will already be labeled.

Step #5: Segregate email accounts (optional)

It’s not uncommon to juggle multiple email accounts. Over the past few years, I’ve had my personal email in Outlook; my high school mountain bike coaching emails on a different address, also in Outlook; and my Gmail, which is non-work business email (e.g., LinkedIn stuff). Now I’ve collapsed all three into my Gmail interface, to take advantage of all the features described above.

That said, I still like to have my personal email separate from business, so I created a rule that adds an “Inbox – albertnet account” label on all emails addressed to my personal address, and has these messages skip the main (Gmail) inbox. As with my other inbox, messages are automatically labeled as they come in, and then when I’ve responded (or have decided I don’t need to) I archive them by removing the “Inbox – albertnet account” label.

If your Gmail interface manages multiple addresses, you can set any of your addresses as default, so when you create a message it’ll come from that address, unless you manually change it for that thread. When you reply to a message, it will be sent from whatever account received the email, unless you manually change it for that thread.

Conclusion

I’ll grant you this has been a long, complicated post. It might be pretty daunting to imagine embracing this approach. But to recall last week’s post, an Adobe study of 1,000 white collar Americans found that on average they spent 8.9 hours a day between personal and work email … wouldn’t it be nice to streamline this? Wouldn’t you rather learn one methodology that makes you more efficient, than waste valuable time on into the future on this unavoidable activity? I’m here to tell you that I’m far more efficient and effective since I adopted Inbox Zero … you can be, too.

—~—~—~—~—~—~—~—~—
Email me here. For a complete index of albertnet posts, click here.