The Daily Parker

Politics, Weather, Photography, and the Dog

Fitbit reports the damage

Scroll down and you'll see that I did not achieve my goal of 25,000 steps on Saturday because (most likely) I ate contaminated kefta kebab on Friday night.

My Fitbit did provide some interesting data, however, that underscores how disappointing the trip turned out to be.

Sleep: I average 7 hours a night, generally. Friday night, more because I had absolutely no responsibilities than anything else, I slept in, getting 9:34 total. But then the sleep chart goes almost full-circle as the Fitbit recorded all my naps. Total sleep from Friday night to Saturday evening: 14:11. Total sleep in Bend: 20:41. (Given that I was only in Bend for a little over 40 hours, I slept through more than half of it.)

Steps: Instead of 25,000 on Saturday, I got 11,633. That includes the one-hour hike Saturday morning when the symptoms first hit me, and a shuffle to the nearest Walgreens to pick up some Gatorade. Do you know how much I hate Gatorade? Less than I hate serious dehydration, but only just.

Resting heart rate: My RHR usually hangs out around 63. Give me a good, painful illness, and that goes to hell: 65 on Friday, 68 on Saturday, and 70 yesterday, despite yesterday being spent mostly in transit.

Weight: Well, here's the silver lining. My body mass has remained frustratingly stable about 3 kg over where I want to be since mid-November. While I expected that to drop some as the weather got warmer, as it has every year, I didn't expect to drop all 3 kilos in one weekend. This may have something to do with me having no solid food from my bagel Saturday morning until I attempted (successfully!) some pretzels, saltines, and a hard-boiled egg yesterday afternoon. I also had a bit of success with a container of steamed white rice when I got to O'Hare. It turns out, water has no calories, and Gatorade has just over 200 calories per liter. So altogether, I had perhaps 1,000 calories in two days, at the same time my body was shedding every gram of food and water that got into my system from Friday night on.

Don't worry, I'm hydrating. I might gain a kilogram back in the next day or two. On the other hand, my appetite hasn't fully returned, so I might keep it off for a while.

Anyway, other than being pissed off about spending my one day in Bend asleep or on the pot (and not the pot one would ordinarily want to be on in Oregon), I seem mostly recovered. It's going to be a beautiful day in Chicago, so I plan to get another 20,000 steps today. And drink a lot of fluids.

Heading home

It's great that I spent 21 of 44 hours in Bend asleep. Yeah, that's just special.

It's a beautiful day both in Oregon and in Chicago today, which is why I'm even happier to be inside the PDX terminal.

Still, the extra-special-fun symptoms I've experienced over the last two days seem to have subsided. I may attempt to eat solid food in a few minutes, which I haven't done since 9am yesterday.

Can I get a do-over, please?

Well, this sucks

The good news is, I've gotten almost 12 hours of sleep in the last 18.

The bad news is, of course, I'd rather be exploring Bend, not passed out in my hotel room clutching my stomach.

It's not alcohol; I had precisely one beer with dinner and one glass of local wine after. And I went to sleep at my usual time (11pm CT/9pm PT). But when I woke up this morning, I felt a general malaise that became, after a bagel and coffee plus a one-hour walk around town, light-headedness, nausea, and unbelievable fatigue. 

I'm now going over in my head everything I've consumed in the last 24 hours and I have a suspect. Still, it doesn't feel like food poisoning exactly, so I'm not entirely sure what's going on.

I feel better now after a 3-hour nap. Making my goal of 25,000 steps seems highly unlikely, but I can still get in another 10k or so before collapsing completely.

Bonus: here's the Mirror Pond, just a few blocks from where I'm staying.

Warm-weather fan

I went to my first Cubs game tonight after not entering the park for an entire season. As I write this, they're up 8-0 over the Reds going into the 9th. But I'm not there, because I didn't dress appropriately. By the end of the 4th inning my teeth were shivering. It's April; 8°C is not that unusual.

I'll be back, when it's warmer. Possibly by then the Cubs won't be in first place anymore. I think it's going to be a weird season.

Ode to the 757

Pilot Patrick Smith wishes Boeing would update the 40-year-old aircraft instead of pushing the 737 into ungainly configurations:

What I think about the 737 is that Boeing took what essentially was a regional jet — the original 737-100 first flew in 1967, and was intended to carry fewer than a hundred passengers — and has pushed, pushed, pushed, pushed, and pushed the thing to the edge of its envelope, through a long series of derivatives, from the -200 through the -900, and now onward to the 737 “MAX.” In other words it has been continuously squeezed into missions it was never really intended for. The plane flies poorly and, for a jet of its size, uses huge amounts of runway and has startlingly high takeoff and landing speeds. Its range allows for cross-country pairings, but transoceanic markets are out of the question.

I was wedged into the cockpit jumpseat of an American Airlines 737-800 not long ago, flying from Los Angeles to Boston. (In years past, coast-to-coast flights were always on widebody DC-10s or L-1011s.) Man if we didn’t need every foot of LAX’s runway 25R, at last getting off the ground at a nearly supersonic 160 knots — thank god we didn’t blow a tire — then slowly step-climbing our way to cruise altitude. What would it have been like in the opposite direction, I wondered — a longer flight, from a shorter runway, in the face of winter headwinds?

The 737’s poorly designed cockpit is incredibly cramped and noisy. The passenger cabin, meanwhile, is skinny and uncomfortable, using a fuselage cross-section unchanged from the Boeing 707, engineered in the 1950s.

I also like the 757s remaining in American's fleet, and I have some problems with the 737s. I'll be on one tomorrow for four hours, with its vertically-misaligned window and cramped seats. Sigh.

Clean your damn data!

Because no one has actually cleaned up a database of IP address geocodes, a Kansas farmer is getting blamed for all manner of bad behavior on the Internet:

As any geography nerd knows, the precise center of the United States is in northern Kansas, near the Nebraska border. Technically, the latitudinal and longitudinal coordinates of the center spot are 39°50′N 98°35′W. In digital maps, that number is an ugly one: 39.8333333,-98.585522. So back in 2002, when MaxMind was first choosing the default point on its digital map for the center of the U.S., it decided to clean up the measurements and go with a simpler, nearby latitude and longitude: 38°N 97°W or 38.0000,-97.0000.

As a result, for the last 14 years, every time MaxMind’s database has been queried about the location of an IP address in the United States it can’t identify, it has spit out the default location of a spot two hours away from the geographic center of the country. This happens a lot: 5,000 companies rely on MaxMind’s IP mapping information, and in all, there are now over 600 million IP addresses associated with that default coordinate. If any of those IP addresses are used by a scammer, or a computer thief, or a suicidal person contacting a help line, MaxMind’s database places them at the same spot: 38.0000,-97.0000.

Which happens to be in the front yard of Joyce Taylor’s house.

And, of course, since most people don't understand (a) default data, (b) data errors, or (c) how anything at all actually works, default IP mapping by MaxMind and other companies (including Google and Facebook) has resulted in people behaving stupidly all over the U.S.

Pro tip: Never live near a major data center.

Reading list

Here we go:

It's also a nice day outside, so Parker will probably get two hours of walks in.