McDonald's Two-Lane Drive Thru - TTAKS by Erin Wade

Drive-Thru Hell

We’ve all had experience with the two-lane drive-thru setup at McDonalds.

(No, not all of us. Certainly not you. I know you don’t ever go to McDonalds. I don’t either.)

I remember back when there was just one lane, and one window. And then, they came out with the two window system, with the promise that it was better, stronger, faster. And it was.

And then, for a little while, there were three windows, because after all, if two is better than one, then three must be better than two. This experiment was relatively short lived, so much so that I cannot recall exactly what happened at each window. I think they took your money at the first one, and you got your food at the last one, but that middle window... random conversation with a teenage employee? (Yes, I could google it, but where’s the fun in that?)

Short lived, but still having required major remodeling efforts at each store that had it. Many still have that middle window, always closed, locked up, vacant, unloved. They sit on the side of the building, an architectural appendix, useless, waiting to burst...

But I digress. Two-Lane drive thrus...

The goal of each of these changes appears to be to move us through the thru more quickly and efficiently; to get us our food and back on the road before we really have an opportunity to think about what we’ve done. Two windows did this, and two windows remain. Three presumably did not, and so the third window is abandoned like a dirty shirt. And now two lanes are here, and they’ve been around for a little while, suggesting they are here to stay. This would suggest that the crack research team at Hamburger University has found the design to be effective. And maybe it is, from a statistical perspective.

But as you sit there on approach, waiting for your turn at the speaker, the two-lane drive-thru demonstrates its true reason for existence: As a litmus test for the average person’s ability to manage their vehicle in tight spaces.

Yes, each and every one of us has learned how to navigate successfully enough to line up the driver’s side window with the speaker and monitor. Check off that particular skill development as done and done. The great tragedy is in what happens next.

The person in front of you then completes his or her order, and of course pulls forward. And then you think "great! Now it’s my turn." And it should be, of course. But it’s not. Because when they pull forward, they only pull forward three feet, afraid of coming into contact with the vehicles in front of them. This leaves you in a position in which you can clearly see the speaker and monitor - maybe it’s lined up with your front bumper or, worse, with your front fender - but you are not close enough to hear it, or for your voice to be heard by the staticky worker on the other end.

Sometimes you are close enough to trip the sensor, and you can hear that disembodied voice speaking, welcoming you to the establishment, like a mirage in the desert, ever present, yet ever distant.

You are also close enough to see something that the driver of the Escalade in front of you cannot see over the massive expanse of unnecessary sheet metal that serves as a hood: they can easily pull forward another three feet.

Three feet! And you know that three feet is all you need, all you’ll ever need, to get up to that speaker, to relay the manifesto that is your value meal order, and get you on your way up to that window. You sit there and will them to pull up, to take that three feet. Mentally you offer them your mind’s eye, psychically providing the opportunity for them to see what you see, to see the huge chasm of space that remains between their front bumper and the car beyond. You become Elaine Benes on the subway, mentally pushing for events, events that will never occur.

And, to be fair and balanced, while an Escalade is a motor vehicle crime against humanity, this same sequence of events happens when the person in front of you is sitting in a Prius.

Often then the line will edge forward slightly, and you can see the opening for the car that impedes your path. Sadly, however, the etiquette on how to merge and who goes first remains, after all of this time, a thing left to chaos. The vehicle in front of you moves forward three inches, only to be cut off by the vehicle in front of them. You fill that gap, putting you closer, ever closer, and still not yet there.

Then there is a break, a shift in the traffic, Janie Escalade/Johnny Prius pulls forward, giving you your opening, your opportunity at that monitor and microphone, and you pull up to order. You hear those magic words "welcome to..." and you start to speak, rattling out your now heavily practiced order, only to realize that you are hearing the speaker on the other lane.

But then it finally happens and you have your order in, confident that all is now right with the world, your trial now complete. Until you realize that you do not have enough room to pull forward, and that it is now unclear whether the next turn belongs to you, or the person in the other lane. You are now the impediment for the poor souls trapped behind you. The great winter of your discontent is now past, but theirs is just beginning.


As I’ve said, I assume that this change must make the line more efficient and decrease the vital time between the taking of the order and it’s delivery; If you have worked in fast food you know that these statistics are of prime importance. Unfortunately, it seems to take absolutely no consideration for the subjective experience of the customer. It misses the fact that, while this process may be faster, the experience feels longer.

Previous changes to the system did not do this. Adding the second window to the original one window, one lane system meant that you were given steps along the way that made you feel like you were making progress. Originally there were just two steps:

  1. Place order and wait
  2. Get to window, pay, get food

Adding the second window gave you the opportunity to do something - paying - on the way to getting to your final prize. It made the process seem like it was underway, in motion, and that you were an active part of it. You may have actually sat in line just as long, but something interrupted the monotony and anticipation along the way. This is the same reason that the big name amusement parks have entertainment options all along the winding, twisting lines for the roller coasters - taking the monotony and anticipation out of waiting.

Instead, the two-lane drive thru adds anticipation where there wasn’t any before - before you have your order taken. It makes it seem longer because you are right there, but you cannot proceed. This may not factor in to the time between order and delivery, but it certainly factors in to the experience. Maddening.

I have no hope that it will change - it appears to be ubiquitous at this point, simply a part of the landscape, a thing to endure.

But not for you, of course. You don’t have this problem, because you never go to McDonalds.

And neither do I.

The Omnibus Podcast - a Review by Erin Wade

Omnibus Podcast - Defenestration

The Omnibus is a new podcast by John Roderick and Ken Jennings. For those unfamiliar with these two gentlemen, this description, by Kim Holcomb on Twitter, sums them up to a "T":

FullSizeRender.jpg

Ken Jennings is likely the better known of the duo due to his record setting winning streak on Jeopardy! During that streak in 2004 he was all over the media, he has participated in multiple other game shows, and he is also an author.

John Roderick) is the lead singer and songwriter of The Long Winters, as well as a veteran podcaster, co-hosting Roderick on the Line and Road Work with Merlin Mann and Dan Benjamin, respectively. Roderick is also a former candidate for the Seattle City Council, a process which he detailed in painfully honest detail on ROTL, and which I talked about here.

The Omnibus is a new take on historical events and popular culture. The show is couched in the conceit that Ken and John are recording an encyclopedia of obscure and ephemeral information about our history and times in the hopes that it will be preserved for future generations - or beings, for there is no assumption they will be human - after what is almost certainly the impending apocalypse that will end our era. As such, almost any errata is fair game, ranging from describing how starlings were introduced to the americas to the "Rachel".

Yes, the "Rachel", Jennifer Aniston’s haircut from the TV show Friends. How is this a thing that needs to be preserved for future? This is part of the the magic of Omnibus - by the end you will understand why.

The range and variation in topics should be a clear sign to listeners that this is not a show that takes itself too seriously. Far from being a dry lecture about a given subject, the Omnibus ultimately plays as all the best podcasts do - it’s about two people, who clearly enjoy each other’s company, talking about something that interests them both. While each episode is nominally about the thing in the title, they all wander far afield, covering topics and ideas that are, to a greater and lesser degree, related to the original subject. The hosts know it when it happens, and you will hear them periodically note that they are, perhaps, veering some distance away from the topic (not that this realization has any impact on the course of the discussion). It’s a little like reading the cover page on Wikipedia, and then following the rabbit hole of links in each article, but doing so while taking with a good friend. If that notion appeals to you - and you know who you are - this show is absolutely for you.

I’m several episodes in at this point, but probably my favorite thus far has been the December 7, 2017 entry on Defenstration.

Full confession here - I’m quite certain I had heard this word before, but if I thought I knew what it meant, I was kidding myself.

Defenestration, my friends, is the act of throwing someone out of a window.

Is it possible to talk about such a thing for nearly 40 minutes? It is indeed, and magnificently so! How did such a thing reach the level at which it requires its own name? When it involves an entire city council, well...

There are many good podcasts out there, and between podcasts and audiobooks I have little free space in my listening time, so I guard it carefully. That said, Omnibus has quickly gained a spot in my regular listening cue. If you like history, but don’t want it take too seriously, Omnibus deserves a listen.

You can find the podcast here, and subscribe to it on iTunes here.

Enjoy!

Riding in Snow - Upright vs Trike by Erin Wade

Winter Wonderland

This was the view as I set up my trike to go out for a ride early yesterday afternoon. I’ve been doing winter biking for the past several years. When I got my Catrike Pocket, one of the things I was looking forward to was this part of my riding experience - Winter riding is great, but there are disadvantages to having a two-wheeled conveyance underneath you in the ice and snow...

Today wasn’t my first cold weather ride on the trike, or even my first one encountering snow, but it was my first out here on the prairie, on a day like this - actively snowing, with the roads as yet uncleared.

I didn’t want to spend a lot of time on the actual road under these conditions - I ride my bike and trike out here on the road all the time, and I find people to be quite respectful, but the earliest snows often find drivers have forgotten everything they previously learned about driving in the white stuff. And, as the picture accurately displays, visibility was not ideal (yup - that’s the sun overhead). So I decided to ride down the wind turbine service roads instead. This involved only a short distance on the road itself. The service roads aren’t long, but it would still get me out and about for a little bit.


Enjoying this post? Check out our Cycling page for links to other cycling articles on Applied Life


Cutting thru the snow is more work than one might realize - the gears you use are lower, and there’s a lot of spinning going on. The section of the road going towards the service road is downhill to get there, and I was a little surprised how much the rear wheel moved around. I was never sideways, but there was a lot of wiggling from side to side (I still have my road tires on the trike).

Once I hit the service road this was the view:

Hoth?

The service roads are gravel, and simply there for trucks to get back to the turbines, so the surface is a bit rougher than being out on the open road. It was passable, however, while I was heading east/west. When the road turned to the north the volume of snow - probably just due to wind direction - was too much to make it passable.

So I turned around and headed back. This was mostly uneventful, except that the downhill section on the way there was now an uphill section. In the snow on the pavement I did finally hit one section where all I could do is spin the back wheel with no forward progress. I tried for what felt like ten minutes (but was probably 30 seconds) to get it to move forward without dismounting, rocking back and forth a bit (it works in the car, so why not here?) but finally gave up, got up, and rolled it forward a few feet. That seemed to do the trick.

I was a little disappointed both in the distance and duration of the ride, so I decided to take out MLW’s upright for comparison. Her bike is a Walmart-special steel Schwinn mountain bike, and I’ve used it before for winter rides. I thought it might be interesting to compare both the experience, and the numbers for the two.

What I found was:

  • The wiggly downhill section on the trike was wiggly on the upright as well, but with both front and rear wheels moving unpredictability.
  • I made it slightly farther on the northerly section of the service road, but it was still pretty much impassable.
  • I didn’t get stuck on the uphill return, but again had both wheels periodically breaking free (I didn’t drop the bike or wipe out - but I certainly have done so in the past on winter rides).
  • The 3-4’ higher you sit on the bike makes a real difference with respect to wind exposure. I think I knew this from a logical perspective, but there was definitely more of a sensation of the wind cutting across me as I was sitting up on the Schwinn.

And the numbers? Pretty similar overall:

Pocket in the Snow

Schwinn in the Snow

On the Catrike the ride took me a little over 10 and a half minutes. My average speed was a little slower, but my top speed was a little higher (not that top speed is a target for winter riding). Being a little slower on average probably had to do with the fact that I tried a little longer to get forward progress on the northward section of the service road while I was on the trike, since I wasn’t originally planning on this to be a comparative test; and it would reflect the time spent spinning on the hill before I got up and moved the trike. In both cases, these events (and picture taking) would also account for the longer stopped time on the trike as well.

So - ultimately the trike appears to have done about as well as the mountain bike from a numerical standpoint. And from a never-threatening-to-disappear-out-from-under-you standpoint, it far exceeded the upright. I think now I just need to consider whether, and what type of tire change to make for the rear wheel to improve traction. I won’t typically ride on unplowed roads, but it would be good to not have to get up and push on a slippery uphill section.

Vacationland - A Review by Erin Wade

Vacationland: True Stories from Painful Beaches

You know who John Hodgman is. I know that you think you do not, but you do.

You’ve seen him in those "I’m a Mac..." commercials as the PC. You’ve seen him as the Resident Expert and the Deranged Millionaire (or Billionaire) on The Daily Show with John Stewart. You’ve heard him doing pieces on This American Life. He’s appeared on TV in Parks and Rec and Community and ever-so-briefly on Battlestar Galactica. You know him.

But you don’t. Not really.

For much of his entertainment career, John Hodgman has been playing characters. Over the course of the past decade or so he has written three books which purport to comprise the sum of all (fake) world knowledge. They are:

These books are delightful pieces, functionally presenting as almanacs with extensive bits of information that are entirely fabricated (though sometimes one wonders - perhaps the city of Chicago is, in fact, mythical). These aren’t just lists of made-up facts, though there is some of that, to be sure; in many cases, the concepts are woven into tiny short stories that can take on a life of their own, and presented convincingly enough that you may find yourself questioning what you think you know.

Because the theme is similar across the three - fake trivia and all - one might be forgiven for assuming that the second and third books are sequels, and more of the same. One might be forgiven, because one would be wrong - the books lay out more as a trilogy, reflecting a progression in the type of information, and in the character Hodgman plays as he writes it. It is not a spoiler (as it is on the covers of the books) to note In the first he comes to you as "a professional writer", and then as a "famous minor television personality" (the second book coming, as it did, after gaining the role as The PC). By the third book he has evolved (devolved?) into a deranged millionaire, the book coming just ahead of the Mayan predicted end of the world.

Ultimately, it’s a good bet that, if you enjoy Monty Python, you will enjoy these books (and perhaps not coincidentally, Hodgman interviewed John Cleese not too long ago).

They are made all the more enjoyable if one listens to them as Audiobooks, as this adds multiple guest appearances, including Jonathan Coulton, John Roderick), Paul Rudd, Sarah Vowell, Rickey Gervais, Brooke Shields, and others, (including Dick Cavett).

And now that I’ve provided you with this background, I have to let you know that this information isn’t a good preparation for his latest work:

Vacationland: True Stories from Painful Beaches

With Vacationland, Hodgman sets aside the fake trivia and gets real. Literally.

Vacationland is a series of essays that centers around his experiences while away with his family in rural western Massachusetts and in Maine. This is too simple an explanation, of course, because on that journey he also delves into the struggles of raising children, of finding one’s way in life, and of losing a parent, among other things.

To be clear, Vacationland, like his previous work, is funny - Hodgman has a way of finding little bits of pleasure and joy in even the most mundane of topics. For example, on growing facial hair:

And I grew my second mustache for the same reason all your weird dads grew theirs: it is an evolutionary signal that says "I’m all done." A mustache sends a visual message to the mating population of Earth that says, "No thank you. I have procreated. My DNA is out in the world, so I no longer deserve physical affection."

It is funny, but it is also wry, very candid, self-deprecating, and emotional. Like his previous works, Vacationland made me laugh, but unlike those, it also made me think and, at one particular point, literally made me cry. I can not recommend it highly enough.

This is work that is similar in vein to essayists like Tom Bodett and David Sedaris; and like David Sedaris, again made better still if you listen to the audiobook, which is read by John Hodgman himself. If you have friends who like to read (or listen) to authors like Bodett and Sedaris, this book would make an excellent gift for the holidays, or for whenever. And when they say "John Hodgman?" You can say:

"You know who John Hodgman is. I know that you think you do not, but you do..."

Old Sounds by Erin Wade

As technology advances, one of the things that I find I struggle with is this:

What does one do with the old technology?

This isn’t a new problem - rather, it’s a familiar one when one looks at things that have become functionally obsolete. Old computers are an issue for many in the first world. Who among us hasn’t come to the point where we have an older desktop or laptop computer that works perfectly well in terms of what it was originally designed to do, but has since been replaced with something newer; that replacement either because the newer device does something - has a feature, or runs newer software - that the older one does not, or simply because we wanted something new and shiny. Some companies actually offer a trade-in program for such devices, but even then, many of us still end up with one or more sad devices sitting in a drawer or on a shelf.

For myself, the recurring concern is an old stereo system. This is a setup that I spent several years on, acquiring the components, purchasing one item and then selling it in an effort to trade up to the next. Ultimately, I ended up with the following components:

For the kids out there, a cassette deck was a device that played cassette tapes. These were things that we used to contain large amounts of the music we wanted (as opposed to what a record label wanted to give us) before recordable CD’s came along. And CD’s were things that held music before we all got MP3 players. Oh, and MP3 players were things your parents listened to before we all just had the music on our phones. Phones were a different thing then too, by the way. Look, they were dark times, and we all lived like savages - let’s not bring it up again...

I’d explain the turntable, but vinyl records are, inexplicably, a thing again, so no need there.

Back when this setup it was originally assembled, speaking of CD’s, this setup also had an Onkyo 5-disk changer (I was fond of Onkyo equipment), but it was apparently mechanically more fragile than the other devices, and so it went to the great maker. But the rest of the equipment soldiers on, stalwart in its readiness to produce great sounds.

But it hasn’t produced sounds in several years.

For a long while it was part of the central sound system that was hooked up to our television, DVD player, and media pc (remember those? Kids, this was a thing... you know what, never mind - google it if you want to know), along with an aux hookup for an iPod. But then a couple of things happened. First, one of the speakers began to fail; and second, my father-in-law got a new sound system for his tv, and wanted to find a new home for his old one - a Panasonic surround-sound setup. It physically fit better into our entertainment center and offered much smaller speakers than the Advents (which I love, but which have always been a decorative thorn in MLW’s side).

So I had the speakers repaired (of course) and moved it all up to my office, planning to hook it up eventually to listen to music while I work. I figured I could hook up an Apple TV to it to allow me to stream to from an iPhone or iPad over airplay, and I’ve even purchased a converter to do this (the Apple TV’s digital audio output not being compatible with the analog inputs on the Onkyo receiver).

But eventually is a non-specific time frame. And wait-time allows for other discoveries.

One discovers while waiting, for example, that one can get a set of Bluetooth over-the-ear headphones for a fairly reasonable price. One can pair those headphones with one’s iPad almost effortlessly, and listen to whatever one wants with no one else complaining about the choice or the volume. And one can use those headphones everywhere in the house, not just in the office. And that, when one does this, one does not have to struggle to figure out where to place the speakers, nor does one have to spend time running speaker wire and sorting out how to hide it (I lack the math skills, and more importantly the will, to accurately calculate the amount of my life spent on that particular activity). And now I realize that speaker wire, also, is a thing the kids will need to google...

Now, I typically embrace new technology. And, in most respects, virtually everything about the advances that replace my old setup is better. I realize audiophiles will clear their throats to utter "well, actually" in preparation for discussing audio quality over Bluetooth, but probably their nurses will wheel them off before they can finish their sentence. The reality is that it’s generally good enough, and the rest of it is so much better. The four devices I have in my list above are effectively replaced by two - an iPhone (or iPad, or whatever) and headphones or a speaker. There are no wires to run, they are much smaller, and they can move with you from place to place.

So why am I pining over this now archaic setup? I suspect that a part of it has to do with the amount of time, effort, and energy that went into constructing it in the first place. For those of us of a certain age and inclination, putting together your audio setup was a fetish-level activity. It was important to have the right speakers, and the right equipment to drive them. Assembling the "rightness" was a scholarly activity, involving pre-internet research. This meant poring over audio magazines and the Crutchfield’s catalog in order to ensure it was all... correct. Ultimately this would give one a setup that pumped the music through the speakers loudly, but without distortion, so that you (and your family, and your neighbors, and maybe the people in the next town) could enjoy it properly.

Properly. Dammit.

And yet, here I am, myself, listening to my music on a set of Bluedio Hurricane headphones that I purchased for less than $30 on Amazon, when I should be setting up that audio system and listening to it that way.

Shouldn’t I?

Pessimist Archive Podcast by Erin Wade

The Pessimist’s Archive Podcast is a treasure trove of historical information about people’s reactions to new technology as it emerges. Before I go into detail on it, here’s a little spoiler: they typically don’t like it.

The podcast has been out for about a year, and it has a... casual release schedule (there are 9 episodes so far), but what it lacks in quantity it more than makes up in quality. The episodes are well researched and tightly produced. The host is Jason Feifer, who is also the Editor-in-Chief of Entrepreneur magazine. Each episode also features a variety other voices from people related to the topic on one way or another, and the delivery is done in a delightful tongue-in-cheek fashion. Episodes run around 30 minutes, give or take.

They also run a wonderful twitter feed that provides details supporting both the podcast and the general concept, like this one:

4 MPH?

Overall, the podcast and twitter feed bring a new perspective to the very common complaints we hear nowadays about how screens, or social media, or fill-in-your-own-example-here are a menace and/or are destroying our society.

Perhaps my favorite episode thus far, unsurprisingly, is Episode 6: Bicycle, which reviews and reveals the severe dangers to society, the economy, and women’s morals, represented by the demon two-wheeler. All from the perspective of the 1800’s mindset, of course.

As is always the case, each episode is also accompanied by a list of links to the articles and references discussed, giving an opportunity for a deep dive into the topic in question (How the Bicycle paved the way for Women’s Rights, might help explain that concern about the impact on women’s "morals", for example).

If the general sky-is-falling perspective on our ever-changing times makes you a little crazy (as it does for me), or if you are just a fan of the bicycle and all of its iterations, I highly recommend checking this out.

Against the Wind by Erin Wade

Life on the open prairie is often a windy affair. This is a year-round phenomenon, to some degree, which is why, when I look out any window of my house I see giant white turbines. But there is some considerable variation across the seasons out here. Mid-summer and, to a lesser degree, mid-winter can have extended periods of relative calm, while spring and autumn kick things into high gear, perhaps feeling the need to make up for the laziness of their seasonal predecessors.

Any cyclist who has ridden for any length of time knows the wind can be a formidable foe, and it can absolutely be a factor in deciding whether one wants to ride at all. This is what I was contemplating this past Black Friday - I wanted to get out there and work off some of the turkey and gravy, but the 20+ mph winds were weighing in against that notion. Still, if one waits for the perfect conditions to do a thing, one will never get to do that thing, so I geared up myself and got out my Catrike Pocket. It also occurred to me that this might be a good opportunity to see what the actual effects of the wind are on riding.

To do this, I stopped and took screenshots of my Cyclemeter readings at three key points in the ride - at the end of the first section, riding into the wind, and the end of the second section, mostly with the wind, and again at the very end of the ride.

I selected my route so that I would be riding into (or against) the wind for the first five-ish miles of the ride. I try to do this in general so that the hardest part of the trip presents early on, when my energy level is at its highest. In this case I would be riding directly against the wind - straight south against southerly winds. Cyclemeter indicates the wind speed for the ride was 26mph.

The Numbers

This is how that came out:

Riding against the wind

The average and top speeds are really the primary areas where the impact can be seen. I’ve ridden this particular route four times prior on the Pocket, and my speed across those rides on the route averages out to 12.22 mph. Here, for the first five miles I’m down to 11.36. Cyclemeter also lets you break down your rides into mile splits, so I can compare the first five miles on this against previous rides, and looking back it’s clear that I’m at least a little bit slower, and in some cases dramatically slower, than on previous rides over this section:

breakdown by mile

Both my average speeds and my top speeds are down from the prior rides. In some cases I have weather data for the other rides to compare against for wind speed and direction:

  • On the 11/19/17 ride Cyclemeter indicates the wind was out of the West by Northwest (WNW) at 14mph, so I would have had a partial tailwind for that section.
  • On 11/11/17 it was South by Southeast (SSE) at 8mph, meaning I was riding partially against the wind, although a much slower wind.
  • On 10/20/17 the wind was out of the south at 8mph - a direct headwind.

The 19th - with the partial tailwind at 14mph - is definitely my fastest ride over this section, suggesting some benefit from having the wind behind you (unsurprisingly). These numbers also suggest a bit of a threshold effect - the 8mph winds (which feel like a relatively still day out here) don’t seem to have much of an impact.

And what about getting the wind behind you?

I took the next measurement 6.48 miles later (these were each taken at convenient stopping points). This segment consisted of approximately two miles heading east, and and four going straight north (the rural roads here are mostly laid out in a grid pattern - makes for ride maps that look like Tetris blocks), putting the wind to my right for 1/3 of the segment, and directly behind me for 2/3. That 26mph tailwind does make a bit of a difference:

With the wind at my back

As you can see, the average speed is up by a couple of mph, and the top speed is way up. In the interest of full disclosure I’ll note that this is (of course) a downhill speed (yes, we do have hills in Illinois). This is actually not far off of my highest speed on the Pocket, which was 31.72mph, and that on a much bigger hill during the 2017 Farmondo put on by the Tempo Velo Cycling Club in Sterling IL.

The wind at your back - at least when it’s a big wind - would appear to make a considerable difference.

The remaining couple of miles of the ride were mostly westward, with the very last half-mile going north (with the wind). My average dropped a scosche, but otherwise the numbers look similar to the prior measurement:

the final results

The Takeaway

It’s not terribly surprising to find that the wind against you will slow you down, and that the wind with you will speed you up. With respect to that we pretty much have confirmation of what would be the expected hypothesis. But looking at this over time does show a few other things that I found interesting:

  • While the headwind slowed me down, it didn’t slow me down as much as I expected. An average of ~11 mph on the Pocket is not awful - scanning back over the year my speeds on similar roads range between ~11.5 and ~14.5 mph. I’m at the slower end here, but not so much so as to make it unreasonable to consider riding.
  • There seems to be a threshold effect - an 8mph wind doesn’t seem to have much of an impact, but higher winds look like they do.
  • A good tailwind clearly does have an impact. This always felt like it was the case, but I am a little surprised about the degree of impact.

An additional observation here for me is the subjective difference offered by the recumbent trike. I’ve loved riding for a long time, but riding on windy days, against the wind, on my road bike, has always felt like a slog. The Catrike was different. Yes, it was more work, and I was riding in lower gears, spinning much more than usual, but it didn’t feel like work the way that it does on my Cannondale. Some of this may be due to the aerodynamic advantage of the recumbent - you are simply not up in the wind in the way that you are on an upright bike. Some of it may also be due to not having to maintain balance in addition to pedaling for forward motion. It’s also possible that there is a difference due to gearing. My Cannondale is old - it’s an ‘87 - and only a 12-speed. The Catrike has 27 gears to choose from, and many of them much lower than those on the Cannondale. It might not be as different if I could grind less and spin more on the upright. Regardless, while I still love my Cannondale, I really love my Catrike.

Ultimately, for me this shows that it’s really worth it to get out even when the wind seems to be working furiously against you. And, since most of it is for exercise, I suppose one could say that the wind is ultimately working with you...

Streamlining the Presentation Kit - Amaz-Play Mobile Projector and Wapow Lightening to HDMI Cable by Erin Wade

As a part of my work I give talks and do training many times a year. One of the things I learned long ago was that you cannot rely on the training venue to have all of the equipment you need to do your presentation. This is true in general - you can bank on the fact that they will fail to have a proper cable or connector or to offer an outlet for your device. The worst example of this was the "conference center" where I asked whether they had a projector I could rent, and they took me to a very dusty closet and said "you mean one of these?"

They were pointing at an overhead projector - the kind that people of a certain age will remember their teachers putting transparencies on to throw them up on a screen. This would almost be forgivable, except it was earlier this year - 2017.

Although it is getting better, historically things became even more complicated if you were bringing along your own equipment to hook up. Many places would happily direct you to the Windows laptop they have hooked up, and ask for your flash drive. I cannot count the number of times I’ve seen the smile first freeze, and then fade from their faces when I’ve pulled out my MacBook or, more recently, iPad, and indicated that I’d be plugging that in instead.

For those reasons I have, for a very long time, maintained my own presentation kit. The composition of this has varied a bit over the years, but the mainstays of it have been:

  • An Apple TV (third generation) and its remote control
  • A power strip with a 10’ cord
  • A projector - specifically a ViewSonic PJD5133
  • HDMI Cable
  • VGA Cable
  • Power cords for the ATV and the projector
  • An Anker 5-port USB charger

(The iPad and iPhone are a part of the mix, but they are always with me instead of being part of the kit).

By far the biggest item in this kit is the projector. It has served me well over the past five years, but it is nearly a foot wide, three inches thick, and weighs more than five and a half pounds. The combination of the projector and the power strip have functionally necessitated that I maintain my presentation kit in a separate bag (in my case, an old Trager Backpack). This means that, whenever I go somewhere to do training, I’m hauling in at least two backpacks. It’s a first world problem, to be sure, but a problem nonetheless.

Given that the projector is the largest part of the problem (no pun intended), that seemed a reasonable place to start. Pica projectors have been around for a while, but they typically have very low light outputs (making them hard to see in anything but a very dark room), and they had historically been expensive. However, it had been several years since I’d looked at them, so I thought I’d give it a shot.

I landed on the Amaz-Play Mobile Pico Projector.

Amaz-Play Mobile Pico Projector

This device had a few key benefits for what I was looking for:

  • It’s small - it will fit in your hand
  • It comes with its own tripod and it will mount to a standard camera tripod
  • It’s powered thru a micro-usb cable. This last part means that I can plug it in to the Anker USB charger rather than needing a slot in the power strip (I otherwise only use two slots - one for iPad and one for iPhone)

And while I was searching for the projector, I also came across this Wapow cable that sends from lightening to HDMI and also plugs in to power.

WAPOW lightening to HDMI Cable

What the cable offered was the potential ability to plug my iOS device - iPhone or iPad - directly into the projector. This meant that I could also pull the Apple TV from the kit and that everything I was using was powered thru USB, so I could also pull the power strip out and just go with the Anker charger. Even with everything plugged in I would still have two ports to spare. The direct HDMI connector also means that it will work in those cases where I’m plugging into a television rather than a projector.

By way of comparison, these are the bare essentials of the old and new projector setups side by side:

One of these things is not like the other.jpg

I’ve had the kit out a couple of times since putting it together, and so far it is working well. The Amaz-Play projector is not as bright as the ViewSonic (of course), but it does seem to be bright enough. Because I tend to be cautious with such things - don’t want a presentation to fail for lack of equipment - I’ve brought the old kit along in its backpack for each of the trainings so far. However, I haven’t needed anything out of it, so it’s looking like that will be able to be left back in the office going forward.

There is a fan in the projector, and it does make some noise, but not anything significant. It does have a speaker, but it’s small, as one might expect. If your presentation includes audio, you may want to plug in a separate speaker (and it does have an output for that). It apparently offers wireless connectivity using WiFi, and there is purportedly an app for that, but I have not used it. The reviews on Amazon mentioning that feature are not kind, and it wasn’t something I planned on using. I typically plug in one iOS device and use the other as the remote over Keynote.

The WAPOW connector does get warm around the HDMI connector but so far that does not seem to be an issue. It does bear mentioning that the connector works for screen mirroring and playing slide decks (Keynote or PowerPoint), but it won’t play protected video content. This means that you can show video thru the YouTube app, but attempts to play Netflix, Hulu, Amazon Video, or anything from iTunes is going to fail. This didn’t matter to me, but it might be a limitation for others.

Trike as Transport by Erin Wade

There are certainly people who use bicycles or trikes as part of their daily transportation. I have fond memories of this myself, riding around the countryside and, later, around my small town with a bicycle as my primary form of transportation for most of my childhood right up until the day I got my driver’s license. It’s a recollection brought forward for me most recently by the show Stranger Things, since I was also a kid pedaling around in between sessions of D&D, albeit with considerably less telekinesis (though not for lack of trying...).

As an adult I’ve had little opportunity to use my various pedal-powered implements as transportation in any meaningful extent. While I’ve managed the occasional trip to the grocery store with a trailer, the reality of extended commuting distances and large portion of life in an urban setting that didn’t (and doesn’t) embrace bikes as transportation means a lot of time in the driver’s seat instead of the saddle.

There is a very real part of me that wishes I had more opportunities to use my pedal-powered options in lieu of my car. When possible I’ve tried to manufacture those opportunities - last summer I rode to several cemeteries in the region as part of my ongoing genealogical research. This can be a fun way to combine activities and feel like I’m making some progress, but somehow it’s not the same as really replacing the car.

Last week, as luck (?) would have it, I had such an opportunity. Both my car, and my wife’s car, had to go in for repairs. We are out in the country, and the repair shop is in town - about six and a half miles away. To limit time off from work I made arrangements to have the work done on both cars in the same day. This led to the following routine:

  1. Load my Catrike Pocket into car number one (both cars are Honda Fits - and the Pocket... well... fits in them). Drive the car to the mechanic’s shop.
  2. Ride the trike back home.
  3. Load the trike into car number two and drive the car to the mechanic’s shop.
  4. Ride the trike back home.
  5. Wait for the cars to be done (its possible I did other things during that time as well).
  6. Ride the trike in to the mechanic’s shop to get car number one.
  7. Put the trike into car number one and drive it home. And...

Ok - so for contininuity and storyline, I really want item number eight to say "ride the trike in to the mechanic’s shop to get car number two". The reality is that what follows includes gathering up my spouse and enlisting her help to gather up the last car. In my defense, however, we had parent-teacher conferences to attend, and I don’t really have an extra seat on the trike for my beloved, and she objected to the notion of being strapped to the cargo rack, so...

But this was still real-world transportation use for my machine, the sort of which I almost never get the opportunity to engage in. As a bonus, the three trips - two back, and one forth - offered up about 19.5 miles worth of riding, which is at the higher end of a day’s riding for me (my average trip in 2017 is 11.71 miles, according to Cyclemeter).

I realized as I was doing it that this was also some of the first times I’d actually ridden the trike in town. Since I just got the trike in June of this year, and the majority of my riding is recreational in nature, and catch-as-catch-can, I don’t venture in to town often - the open road is both more alluring and more convenient. I’m pleased to say it feels little different from riding a regular, upright two-wheeler in town, something, as I noted above, I had done many times before. Now I just need to find less costly reasons than car repair to ride rather than drive...

Files, iWork, and Dropbox - Resolved by Erin Wade

At the beginning of the month I wrote about an issue with using Dropbox in the iOS 11 Files app with iWork documents in a shared Dropbox folder (yup - that’s a long, complex sentence to parse, made longer still by this parenthetical observation about it... sorry).

This issue appears to be resolved with the most recent update to the iOS Dropbox app, version 70.2.2,which came out earlier this week. I’ve had a chance to play with it for a few days now, including doing actual work, and it appears to be functioning perfectly.

What this means is that one can now open, edit, and save-in-place documents from iWork files that are stored in Dropbox on an iOS device. This seems a relatively simple thing - we’ve been doing it on computers for years prior to the development of the iPhone and iPad. However, it has been one of the key remaining limitations to the iPad when using it for work activities, particularly in conjunction with Dropbox. As I mentioned when I brought up this issue earlier in the month, the process for using these documents has looked like this:

Depending upon the app one uses, for much of the history of Dropbox on iOS, if one has wanted to work on a file stored in Dropbox, it’s been a multiple step process:

  • Export the file from Dropbox into the app (which typically opens a copy of the file in the app)
  • Perform the edits one wishes
  • Export (copy) the edited file back to Dropbox
  • Delete the copy from the app

The long dark winter of toiling at copy deletion on the iPad has finally come to a close!

Too dramatic?

Probably so, but in reality, it is actually a pretty significant change. I have been using an iPad for work since 2010. Initially it worked as a laptop replacement, but at this point it has largely replaced both my laptop and my desktop. I have a handful of tasks - mostly legacy activities that simply require older machines to run on - that I still need a Mac for, but the overwhelming majority of my work is done on an iPad or an iPhone. And to be clear, the multi-step process above wasn’t something that was preventing the use of these devices for work, but it was the rare, remaining activity in my regular workflow that was more complicated on iOS than on OS X.

Using All the Gears... by Erin Wade

I got my Catrike Pocket in early June of this year. With a handful of exceptions - primarily days in which the Pocket was in need of some sort of minor repair - it has replaced my 1987 Cannondale SR400. I don’t have the prodigious mileage numbers of some, but when I have been riding this year it’s almost always on the trike, and my personal mileage is up considerably from the last couple of years because I’m early enjoying it.

In my eagerness to get and start riding it, I simply started out with the setup that it had when I bought it. As I understand it, the trike had been owned by a woman who didn’t ride it, and then given to my seller, who took it for his wife who also didn’t ride it (the tires still had all the little nubbins on it when I got it). He’d adjusted the boom on it - the telescoping shaft that has the pedals on the end - for himself, and we seemed to be of similar size, and since I wanted to get out there and start riding, I went forward with that setup.

I fairly quickly realized that I was having trouble getting into the lowest gear on the big ring, and top gear seemed a dubious endeavor as well. Still, I was having a lot of fun, and with 25 of the 27 gears to choose from there was still a lot to work with.

But over the past month I noticed - with the increased riding - that I was starting to get some pain in my knees. This was relatively mild, and resolved easily with ice and a bit of ibuprofen, but this was also new to me. A bit of homework suggested that my pedals were in too close. I went online to find some positioning guides and got things set out to where it looked like they should be. In order to test it out I went out for a ride. I planned on 13-14 miles, figuring that was long enough to see if my knees were managing things better, but no so long that it would occupy the time I’d need to make further adjustments.

What I found was two things:

A -My knees felt just fine (yay!), and; 2 - I now had access to about 12 of my gears, with an unpleasant grinding if I tried to get to others.

I spent a little time at the side of the road trying to make derailleur adjustments, to no avail, and tried more focused work on this when I got back to the garage. As is too often the case for me, after struggling with it for about an hour or so, I decided to look things up. I fairly quickly came across this video from the folks at Utah Trikes. I realized the error of my ways right at the point where they start talking about how to find the master link in the chain...

Being new to trikes, and given my tendency to dive in and ask questions later, I was not aware that an adjustment in the boom position would require an adjustment in the chain length as well. I don’t know where I thought the extra length of chain was going to come from - perhaps the Catrike comes with a mystical bag of holding that hides away the extra chain until it’s needed?

Perhaps not.

And once we’re at tasks like adjusting chain length, my course of action is clear: I’m headed to the bike shop. I have neither the tools, skills, nor extra length of chain that would be needed to undertake this task. Also, as I periodically have to remind myself, it’s often much easier, and certainly less frustrating, to let a pro handle things for you.

So - I popped the trike into the back of the car and headed off to Meads Bike Shop in Sterling, which is the localest bike shop that handles recumbents, and specifically Catrikes. The folks at Meads were great! An overnight stay - and one ride out on the Cannondale in the trike’s absence - and we were back in business, now with access to all of the gears.

I’m finding, with things set up properly, that the knee pain is no longer an issue. I’m also finding that I can stay on the big ring without mashing quite a bit more of the time on Northern Illinois’ relatively level roads. I suspect I was missing more of the smaller cassette gears than I thought.

Time will tell whether this makes a change in actual riding performance - if anything, I suspect it will make me a little faster on average. In any case, it turns out that life is better when you get to use all of your gears

Lack of Support (TTAKS) by Erin Wade

The 12.9" iPad Pro was released in November of 2015 - nearly two years ago. One of its many key features was a new, full-sized virtual keyboard configuration. As a regular user of the iPad for work, this was a huge leap forward in typing on glass.

Nearly two years in, as one might expect, virtually every app available for the iPad has been updated to support the full keyboard configuration. Virtually every one.

Virtually.

The standouts? On my iPad Pro there are two that are notable:

  • Facebook
  • Mint

This might - might - be considered forgivable for the Mint app, which is primarily a dashboard for looking at your financial accounts. But Facebook?

Open the Facebook app and you are greeted at the top of the timeline with a box that asks "what’s on your mind" (or whatever this month’s vapid prompt is). It immediately invites you to write something about your day. Unfortunately, if you are interacting with the Facebook app on your 12.9" iPad Pro, tapping into that box gets you a keyboard that looks like this:

Why so much space?

This ungainly laid out key formation is the one designed for the 9.7" iPad and, when displayed on the much larger iPad Pro screen, stretches the keys out to a distance that might be useful for Andre the Giant, but is quite a reach for a person with hands that are a perfectly normal size.

One might ask whether Facebook is possibly unaware that Apple released this larger version of the iPad some 23 months ago - perhaps they are busy sorting through other issues, and so have missed this development. One might think this until one has to contact someone thru Facebook Messenger.

Facebook Messenger, of course, is an app owned and operated by Facebook. An app which, incidentally, has been updated to work with the iPad Pro’s keyboard.

Messenger seems to have been updated

Ok, so, that not being the case, maybe it’s just that Facebook hasn’t had an opportunity to update the app.

Not once. Not once in the 144+ times they have updated the app since it was created...

Version 145.0...

So to be clear, this company makes an app that invites you to type things, has already written the code for the new keyboard and put it into place in another app, and updates the Facebook app approximately every other day, but can’t seem to find the time to make this change.

The living definition of a first world problem? Absolutely. But this is a company that a huge percentage of the country interacts with on a routine basis. Of course, we’re not their customers - we pay nothing for it. Facebook’s customers are the advertisers that buy space in your timeline. But they need our eyes, our attention, to sell. They might not to consider stepping up and making things more pleasant to use.

Things I Learned this Morning - Rainy Day Ride by Erin Wade

October is a tough month for cycling in the Midwest, specifically for finding openings in the rain that correspond to openings in the schedule. Today presented a forecast of rain throughout the day, but there appeared to be a tiny opening between weather systems on the radar. I decided to take that opening, and rushed out to get on the trike.

I learned or realized several things as a result of this experiment, and they are, in no particular order:

  • My Columbia nylon "noisy pants" are not nearly as water resistant as I thought they would be.
  • I do not own any actual rain gear.
  • Fenders might be a more worthwhile accessory that I had originally thought.
  • A break in weather systems on the radar does not necessarily equal a complete break in the rain.
  • My accessories that claim to be waterproof/resistant - my lights and iPhone 7+ - appear to be good to that claim, at least for this short ride. And...
  • A visible lightening strike in the distance is a terrifying thing when you are sitting on the open road. On a metal frame. A wet metal frame...

It’s the last item that ended the experiment. I turned tail and went home. I had originally planned on a short ride - about 7 miles - that I knew would turn me around quickly, but I bailed a little over two miles in.

Still - getting some time on the road - wet or not - is better than getting none at all.

1AC73946-E16F-4080-A73E-0404110B2C22.JPG

I swear it seemed like a good idea at the time... 

Shedding Light on the Trike by Erin Wade

When I first got my Catrike Pocket it had an inexpensive lighting setup already on it. This consisted of a mount that held a small flashlight and also held a computer on the accessory mount up front, and a flashing rear light mounted on the rear frame.

Initial Lighting Setup

I started out simply using this setup. I don’t typically ride at night. However, I suspect like most people who ride on the road regularly, I am concerned with being visible to others as much or more than helping with what I can see. Having lights, in addition to a flag, seems a good call on the open road.

My first change was not planned. The taillight apparently was not happy in its relationship with me, and chose to leave me in early August. To be fair, there had been warning signs that things were not going well - it had fallen off the trike on a particularly rough patch of the Perryville Road trail in Rockford, making me stop and pick up the pieces. But when it left, it was truly gone, which is to say it fell off somewhere along a trail and I have no idea exactly where. I noticed it missing when I got back - it didn’t even leave a note.

I replaced the taillight with the Blitzu Cyborg 168T. This light had good reviews on Amazon, looked to have a nice, stretching, adjustable mounting system1, and it was rechargeable. It came from Amazon as advertised, and I added it to the back of the Trike. The one change I made here was to put it up on the horizontal crossbar rather than the vertical, which put it a little higher on the trike, hopefully in a better sightline for drivers coming up behind me.

Blitzu in place
Blitzu close up

I’ve been pleased with how it works thus far. The only situation in which it had failed on me was when I rode in the Farmondo in Sterling, IL. I rode the 43 mile course and somewhere in the 3 hours and 24 or so minutes of the event the taillight gave up the ghost. It must have been near the end of that time, however - there were two stops along the course, and I don’t recall it being out on either of those.

As the days have been getting shorter, I also started to think about the lighting up front. The original setup has been fine for riding during the day, I think. But, while I don’t really plan to do nighttime rides per se, it’s becoming a more common occurrence that the daylight is running out before I get home. Given this, it seemed like a good idea to have something that would make me more visible at night, and would let me see things better in the dark as well.

I returned to Amazon2 to see what they had to offer in this department. My primary criteria were brightness, a good mounting system, and that it be rechargeable. There are a lot of bike lights on Amazon. Ultimately I landed on this light by INBIKE. It’s bright - brighter than most of the lights I looked up, has side markers, is water resistant, and can also be used as a flashlight. And the mounting system looked convincing enough on the site1.

I didn’t want to remove the old light, mostly because I wanted to keep the computer mounted there, so I also ordered a Minoura Accessory Holder to mount it to. This also has a couple of additional benefits:

  • It puts the light up higher, further enhancing visibility; and
  • It has space for at least one additional item to be mounted to it. I’ve considered putting my iPhone up front rather than off to the side, for example, so this would offer that option in the future.

Everything came together well - things mounted as expected, and seem to attach appropriately. This is the initial setup I’ve put together:

Before:

One Lonely Light

And After:

And then there were two
Two from the right
Two from the left
(I adjusted the angle of the top light after I took that picture)

Probably the most fiddly part of getting things right was the Minoura Accessory Holder. I’m still not certain the angle that it sits at is perfectly vertical (this is a need I have - don’t judge me). In addition, the screws in it take three different sizes of Allen wrench, and you have to use all three to get everything tightened down. However, once it’s in place it seems to work well.

Of course, once I had it all in place I had to give it a try:

Light up the prairie

Out in the dark of the open prairie this brightens things up pretty nicely. I rode about a half mile in each direct to try it out, and I certainly felt comfortable that I was seeing far enough ahead of me to judge the road - I was not able to outrun my headlight.

Why Rechargeable?

I noted that being rechargeable was an important criteria for me with both lights. I’m sure opinions vary on this point - I am old enough, and geeky enough, to remember the debates over whether it was better for a cell phone to have a removable battery. But for me, being rechargeable has multiple benefits:

  • I can plug them in after each ride to be sure they are fully juiced up for the next trip. With regular, removable batteries you are left with whatever is left from the last usage, with no way to know how much that leaves you, which means...
  • I don’t have to carry spare batteries with me. AA and AAA batteries aren’t especially heavy or bulky in small quantities, but they do take up some space, and remembering to replace them as you go is something that is easy to not do.
  • I can charge them in my car. In most cases, my car also doubles as my bike prep station. I keep my air pump, helmet, gloves, chain oil, etc, in there. I also typically plug in the lighting items in the car (I have a separate battery for this purpose), so I always have them with me, fully charged, and ready to go.
  • I can plug them into my power pack if they run out while I am riding, and recharge on the go. While I don’t want to carry AA/AAA batteries with me, I pretty much always have the power pack on the back of the trike. This would also be a benefit for folks running with hub generators.

The debate over removable phone batteries seems to be resolved, so maybe this isn’t the question it once was. Still, there seem to be plenty of bike light options that still have removable batteries out there, so...


  1. In my experience, the mounting system is at least as important as the product itself when it comes to bike accessories. I’ve had excellent lights, for example, that have been nearly unusable because it’s too difficult to get them to strap properly to the handlebars or other mounting points.  

  2. For the record, I absolutely believe that you should support your local bike shop whenever possible. I do this where I can for repairs, tune-ups, and so on, and I find them to be great. Unfortunately, our most local bike shop is a half-hour away, and not in a location that I routinely travel to for other things.  

Files, iWork, and Dropbox Issues by Erin Wade

One of the banner features of iOS 11 is the addition of the new Files app, which works in a fashion similar to the Finder in Mac OS, and offers the promise of giving a central location for all of your file access needs in iOS. For those of us who have been shepherding around files from app to app ove the past seven years, this is an exciting prospect.

It is often the case that other developers aren’t ready to take advantage of the new features in iOS on day one. Sure enough, Dropbox was not ready to fully integrate into the files app on the iOS release date. However, I was pleasantly surprised to see that Dropbox shipped an update within a week of the emergence of iOS 11, promising to integrate with Files and, perhaps more importantly, allowing save-in-place.

What does this mean?

Depending upon the app one uses, for much of the history of Dropbox on iOS, if one has wanted to work on a file stored in Dropbox, it’s been a multiple step process:

  • Export the file from Dropbox into the app (which typically opens a copy of the file in the app)
  • Perform the edits one wishes
  • Export (copy) the edited file back to Dropbox
  • Delete the copy from the app

Much more complicated than the simple open-edit-save routine that one would prefer. What’s more, it’s easy to omit the last step in the routine, and end up with a batch of leftover files in the app, visually clogging up the works. To be fair, Dropbox has offered an API to allow apps to save into Dropbox - 1Writer, the text editor I use to write these posts, is an example of this. But Dropbox has never before embraced save-in-place for apps like Apple’s iWork office suite, which I use routinely for work. This means I’ve been routinely doing the dance I described above for the past several years. To say I was excited about the prospect of no longer doing this would be an understatement.

Unfortunately, it doesn’t work.

Let me dial that back just a bit. Strictly speaking, it does work to open an iWork file from Dropbox using the files app, and that file saves back to the same location in Dropbox when you close it. Just the simple open-edit-save routine that one hopes for.

Where the problem comes in is that this only works in an unshared Dropbox folder. Use a shared folder - arguably a primary reason for Dropbox’s existence - and things go directly south. It is possible to open an iWork document from a shared Dropbox folder using Files, but that’s where the joy ends. It is not possible to modify the file and save back.

When one opens a document under these circumstances one is greeted by a warning indicating "Couldn’t connect to iCloud".

couldn't connect to iCloud

Disregard that warning, and attempt to make any change at all to the document, and you’ll interrupted by a warning indicating "Couldn’t Connect: Pages [or Numbers] couldn’t connect to iCloud. There may be a problem with the server or network" or "Couldn’t Connect: Pages couldn't Connect to iCloud. Try editing this shared document later, or edit a copy."

couldn't connect 1

couldn't connect 2

The second warning suggests that the app (Pages, in this case) thinks this is a shared document - one that is being shared by multiple people using iCloud. It’s not - the only shared thing in the scenario is the Dropbox folder it is resting in.

Turn off the integration between Files and Dropbox and things continue to work the way they did before iOS 11 (well - except for Keynote Files, which now inexplicably cannot be uploaded to Dropbox from the iOS app at all, but that is outside this discussion). It’s possible that this issue is only occurring on my devices, but I suspect this is not the case. I’ve filed but reports with both Dropbox and Apple, and I’m hoping others experiencing this will do the same to get this issue addressed quickly - I’d really like to see this work as promised.

Trike Storage by Erin Wade

Riding and living with a recumbent trike is different from from the upright variety in a number of ways, and one of those is storage. There exists a cornucopia of storage options for upright, two-wheeled cycles, ranging from very simple options to mechanically complex.

My Catrike Pocket takes considerably less vertical space than an upright bike, but it’s also considerably wider. Out at the Homestead we have a fair amount of space, but useful storage area outside the house is mostly limited to our small garage.

While, as noted, there are certainly a number of fancy ways to store a bike, I’ve always been partial to the simple approach offered by a ceiling hook. If one has a crossbeam to screw a couple of these in to, hanging up a two-wheeler becomes a simple exercise of identifying a location where one hopefully will not repeatedly walk into the bike (a step I may have failed at a time or three in the past), measuring out the distance between the wheel centers, and mounting the hooks. Not fancy, but a pretty reliable system, even in our limited garage space:

bikes hanging out together

The layout of the trike complicates things. The three wheels do not run in a line, so they cannot be managed by simply putting hooks in a crossbeam. What’s more, the distance between the front wheels does not match the distance between the beams, so mounting each wheel to immediately parallel beams wasn’t an option either. And given that most of the airspace that doesn’t have people walking through it regularly is already occupied by the other bikes, having the trike hang that low wouldn't have been a great option anyway.

I considered mounting along a wall instead of in the ceiling, but the layout of the garage is such that any wall space that isn’t occupied by stuff already is unoccupied for a reason - mostly because a car has to pull up close to the wall in that space. While the trike isn’t tall, it would stick out far enough to impede that sort of use. It was going to have to be mounted above, high enough to prevent noggin-knocking, but not so high that I couldn't get it up and down (I am not a tall person).


Enjoying this post? Check out our Cycling page for links to other cycling articles on Applied Life


My solution was to install 2x4’s across the top end of the cross beams - two of them running side by side, and the third set back at the rear wheel’s center. This arrangement allowed me some play for the mounting of the hooks side to side as well.

Hooks! Nothing but hooks!

This position gets the Catrike up high enough that I can walk under it without fear of hitting my head.

Hello!

Hello again

It also sets it high enough that the car can fit under it (since my bike storage needs are now spreading out into the car area of the garage).

Catrike over car

I was initially a little nervous about the fact that the trike is hanging right over the windshield of the car, but it’s been there for months now, without issue. Also, there really wasn’t much by way of other option - moving it further back, say over the roof of the car, would interfere with the travel area of the garage door.

To get the trike up on the hooks, I have to pick it up, flip it over, and then lift it above my head - a variation on a clean and jerk. I hold it by the crossbar across the top of the seat back, and the accessory mount on the boom. Fortunately the Pocket is only about 33 lbs from the factory, and probably around 35 with my bags and accessories on it, so this isn’t significantly harder than lifting the two wheelers. Lining up the three wheels with the hooks was a little more challenging at first, but that’s gotten easier with practice.

Overall it’s been a good solution. Getting it in place took a bit longer than my usual bike system - lots of measuring to make sure everything lined up before I finalized things, and of course considerably more cutting, drilling, and driving of screws. And I am now running out of ceiling space. I would need to get more creative if I were to get another trike (but that never happens, right?).

A Brief Flirtation with Google Drive by Erin Wade

As is true for most of us, I have my systems for doing things, and I get comfortable in those systems. Still, it is good to periodically check out other options to make sure one is not missing out on something better.

I've recently been exploring the possibility of changing my email service, and I was considering the option of using Google's email service - not basic gmail, but rather the email thru their G Suite service, which allows you to use email addresses based in your domain (e.g. that end with your own address rather than "gmail.com").

G Suite, as the name implies, doesn't just offer email, but an entire office suite of features, many of which present the option of potentially replacing systems I already use. They have a secure video conferencing service (Hangouts Meet), they have their suite of office software, and they have an online file storage service, Google Drive.

Some of these things are of interest to me, while others are not. For example, I'm open to exploring Hangouts Meet as an alternative to our current service, but prior experience leaves me with exactly zero interest in Google Docs, Sheets, or Slides. The feature set in Apple's iWork suite is perfect for me, and it's integration into iOS devices, particularly the iPad, makes it a solid winner for me every time. I also am well aware, both from personal experience and from the reports of others, that Google has historically been slow to update the iOS versions of their products to use the features available on the iPad.

Among the products in G Suite is Google Drive. Aside from looking up documents from my kid's school, I had very little experience with this service. I'm a long-term user of Dropbox, but as I said at the beginning, it's good not to let comfort keep one from exploring other, potentially better options. Since, like most of the free world, I have a personal Google account, I also technically have a personal Google Drive. I decided to play with it a bit and see what I thought.

I downloaded the app to my iPad and made a couple of documents to put into the drive for testing purposes. Some of what I found was what one might expect. It handled PDF documents just fine - you can render a preview of the document, export it to another location, etc, just as you might expect.

The iWork files were another story entirely.

I specifically made up a Pages document for the test. What I found initially was that there is no preview option for a Pages file - rather, Google Drive just tells you that it is an "unsupported file type".

Unsupported File Type

This isn't entirely surprising in and of itself. iWork files, as I understand them, are actually packages, and in the past that has confused some file systems. But it is inconvenient if you want to take a quick look at the document before opening it to make sure it is what you want. Dropbox and iCloud (naturally) readily render previews of these files.

While this is inconvenient, it is not necessarily a deal-breaker. I'd prefer to be able to preview my iWork files, since I use them regularly, but there isn't that much confusion between one file name and another for me.

But then something else happened: The Pages document that I had entered into Google Drive started duplicating itself. The first time I tried the app it multiplied the file into some 40 or 50 copies, and I said to myself "well, that's that, then" and deleted the app from my iPad. After a few days, and a little bit of thought, I considered the possibility that the experience might have been a fluke, so I tried it again, this time bringing files into the app in multiple ways. When I sent a copy to the app directly from Pages using "Send a Copy", it did not appear to make duplicates (though it did, inexplicably, append "-1" to the file name, despite there being no other file with that name in the folder). However, when importing from Dropbox what I found was that, it after it was sitting in Google Drive for a few minutes, it began to make multiple copies of that file without being asked to do so.

Files duplicating like bunnies

I'm not sure why this would occur, but if I were to consider Google Drive as an option for me, it would be in place of Dropbox, which would mean that I'd be sending a lot of files from Dropbox to Drive. I love The Tick), but I certainly don't need a replay of the attack of Multiple Santa to occur in my file storage.

Of course, there is also iCloud Drive on the iPad. What I found there was that any attempt to import a Pages document into Google Drive from iCloud Drive caused the file to simply hang there, with its progress bar seeming to be finished, and yet never fully resolving. This was only true for the iWork file. I was able, for example, to import a PDF from iCloud into Google Drive just fine.

One could argue that I was functionally warned up front that Google Drive wasn't going to play well with my files with the indication that the Pages document was an unsupported file type. I suppose that is true, to some degree. It's worth noting, however, that the iWork suite - Pages, Numbers, and Keynote - has been around now for over a decade, and it comes free with the iPad - this isn't a new product, nor is it obscure, so it seems reasonable to ask why a product that presents as a general storage tool would not be prepared to support these file formats properly. One suspects, if one is conspiratorially minded (as one might be) that it is because Google would prefer one to use their office suite.

A quick check of the weather finds that Hell has not, in fact, frozen over yet, so that won't be happening on my iPad.

So, as the title says, this was a brief flirtation with the product. I might have been able to live without the ability to preview my iWork files - though in retrospect, I do use that feature quiet frequently. Not being able to reliably import my files, and finding them duplicating like bunnies, however, largely seals (or, rather, breaks) the deal.

You're Never Weird on the Internet (Almost) - A Review by Erin Wade

Weird on the Internet

This one is a memoir, written and read by Felicia Day. Odds are good, if you are reading this, that you know who Felicia Day is, but if not, you may have seen her in:

...And many, many others. Basically, if it's geeky and good, Felicia Day has very possibly been involved with it.

This particular book is, as mentioned, a memoir. It recounts her life, beginning from a childhood in the Deep South, home schooled and living a self-described off-kilter life, and continuing up through her professional career, into very nearly current day (the Audiobook was released in 2015) and reflecting her struggles with Gamergate.

Anyone can relate the details of their life, moving from time to time and from event to event. You've probably had an uncle or grandparent do this to you at family gatherings while you desperately looked for some means of escape. What so often (if not always) makes the difference is the telling of the story. And it is in the telling that this book truly shines.

It's a rare book that can truly make me laugh out loud, but this did on multiple occasions. The writing is quick and delightfully clever. She manages to be both wonderfully self-deprecating and reflect pride her accomplishments, sometimes simultaneously. As I mentioned before, it's read by Felicia herself, and this magnifies the telling - like the best audiobook performances, the narration feels like a conversation, a storytelling, not a reading. It's intimate, familiar material for her, and she delivers it with all that entails. I was genuinely sad to reach the end of the book.

As a bonus, because the audiobook was recorded after the tree corpse version's release, there is additional material about events that occurred as part of her book tour. These are very fun as well.

So look - if you are reading this, you probably already know and love Felicia Day's work. You owe it to yourself to pick up (or download) this book.

Station Breaker - A Review by Erin Wade

Station Breaker

Station Breaker by Andrew Mayne is a speculative fiction piece surrounding a private company astronaut, in a near future setting, where trips to and from space are handled by a Space X-like company. The setting is somewhat reminiscent of The Martian, in that it presents bits of technology that might not quite yet exist, but you know are just over the horizon.

That setting in time, however, is where the resemblance ends. Astronaut David Dixon is on his first actual space mission and, even before liftoff, things don't seem quite right. Why is the mission commander, a seasoned NASA astronaut, surreptitiously packing along a pistol?

This story is a breakneck-speed adventure from start to finish. Setting development is efficiently handled, giving a feeling for time and location while trusting the reader to come along quickly, and then never looking back or slowing down. The narrative is in first person, mostly present tense, giving the impression you are seeing things as David Dixon sees them, and keeping you directly in the moment. You, as has David, have been dropped into a very difficult situation with no explanation of what is really happening, nor of why, keeping you on the edge of your seat.

For the hard science fiction aficionados there is real time and attention paid here to the physics of things, both in space and otherwise. Still, this is done in a way that won't be intimidating to readers unfamiliar with these components - if proper physics is important to you, it's there. If it isn't, you won't be forced to pop over to iTunes U and take a course to understand what is going on - it's nicely laid out mostly as color to the overall story, and briefly, clearly explained when it's more important to what is going on.

The physics, and the story, don't only happen in space. This story rolls its way across multiple locations, Indiana Jones style, with some considerable effort on the part of our main character. It's an adventure from moment one.

As (almost) always, I experienced Station Breaker via audiobook. This story was my companion for many a bike ride thru the countryside (one ear only, the other open to the road, of course). It is read by Kyle McCarley. He narrates a number of audiobooks on Audible - 61, based on a narrator search - but this is my first experience with him as a reader. It sometimes takes me a little while to adjust to a new reader - each narrator has their idiosyncrasies, and while an audiobook is certainly the presentation of the author's material, it's also a performance, and the narrator is absolutely a factor in the experience of the book. In this case, I enjoyed his voice, but initially found his way of emphasizing certain words - particularly the word blood (which appears several times early in the book) - took a little while to adjust to. However, I often find that, if I press on a bit, I do adjust, and this was the case here. And in fact, given that time I found that Mr. McCarley does an excellent array of voices, and is able to maintain them consistently throughout, which is certainly not the case for every narrator.

All in all, the book was an excellent companion for multiple rides. It ends on a bit of a cliffhanger, and there is a second book in the series - Orbital - which I have lined up in my cue. Notably, the second book is also read by Kyle McCarley, which offers a nice bit of continuity - it can be somewhat jarring when the narrator changes partway thru a series and all of the characters you've come to know sound different.

If you are looking for a high-adrenaline thrill-ride, with a bit of a science fiction angle to it, I can happily recommend Station Breaker.

Siri is not a Morning Person by Erin Wade

I am an early riser. This wasn't always the case - into my early 30's I was a night owl, and would work or play computer games well into the wee hours. Changes in work schedules over the last decade and a half or so have required early rising by necessity, and repeated practice has resulted in a change to my overall circadian rhythm - I'm typically up by or before 6 AM whether I need to be or not.

On workdays, when I'm in the process of getting ready for work, I've gotten into the habit of asking Siri to check the time. Most often she simply pleasantly chirps out the hours and minutes in her delightful British accent (yes - my Siri has a British accent. Doesn't yours?). But I'm clearly dragging her out into the world far earlier than she'd prefer, and sometimes she lets me know this:

You Woke Me Up, Dude

Sometimes it's this simple protestation that she was still resting when I invoked her - perhaps a not-so-subtle attempt to apply a bit of a guilt trip on me. Still other times she is more explicit about her opinion on what should be occurring at the time, and I feel like she's implying that it should be true for me as well as she:

time to still be in bed

I'd be a little irritated with her if I didn't find myself actually agreeing. Of course, if she's going to have such clear opinions on how early we should be getting up, perhaps she'd like to facilitate a change by doing my work for me. When I suggested this, however, she was unequivocal:

no I can't

I'm a little hurt. Couldn't she give the common courtesy of at least suggesting she could try?