There’s nothing quite like running on a trail. I love sprinting through the woods as fast as I can, just trying to avoid all the roots and rocks littering the ground. It requires fast thinking and good instincts to avoid a misstep that could lead to twisting an ankle, and I just find it incredibly exciting and invigorating.
I’ve run the DC Cherry Blossom 10-mile race several times, and when the trees are in bloom it’s a gorgeous run… But it’s still just one for after the other on pavement. The scenery changes, but each step you take is just like the last, and that can’t help but get monotonous.
This came up because I was talking with a few of friends about maybe signing up for a Ragnar Relay later this year, and the debate was whether to do the road or trail version. I’m emphatically in favor of the trail race. They both have you covering ~200 miles in two days with a team of 8-12 people, one runner at a time. But the road race has the runner going from point A to point B on roads and bike paths while the rest of the team shuttles to the next stop in a van to prep for changing runners. The trail race has everyone staying at a central campsite, and the runners head out on a trail that loops back to the starting point. There are multiple trails of varying difficulty and everyone on the team eventually does each of them. But while the runner is out, instead of sitting in a van the rest of the team is hanging out around a campfire.
Which would you choose?
It’s been a few months since I posted. Oops. I’ll try to get back into the habit of it…
In the meantime, here’s a picture of me as a giant:
Someday I’d like to become conversational fluent in another language, and proficient at a musical instrument (again…I used to play saxophone and trombone in high school). Automattic gives us a ~3 month paid sabbatical after working for the company for 5 years. So in ~4 years that will be part of my plan for my time off. In the meantime I’m learning Danish and Dutch slowly via DuoLingo.
via Daily Prompt: Someday
I got a Home for Christmas. For those who don’t know, and are too lazy to click-through to the link, it’s a voice-recognition device from Google that sits in my living room listening to everything I say. It’s only been available for a few months, so there’s not a ton that it can do yet, but that’ll get better over time. Here are a few of my initial impressions:
- The speaker is better than I expected, completely usable for playing music. You can also tell it to play music on the Chromecast (which I have connected to my stereo speakers), but using the built-in speaker is slightly easier.
- In general it’s context-aware when you tell it to play/pause/etc, but it gets a little confused when you’re casting to multiple destinations. I was casting pictures to my TV and music to the stereo, and I had to be more explicit than I expected to make sure I was controlling the right thing. At one point it also tried to start playing music locally.
- Google Photos needs to really improve their slideshow casting capabilities. It’s cool that I can say “Hey Google, show my Christmas pictures on the TV”, but then it only showed them in reverse chronological order and didn’t seem to offer any way to shuffle them. And it stopped after (I’m guessing) 50 pictures. I’d love to have it throw up a random slideshow that plays for hours. That’s what I do with the PC hooked to the TV, but I can’t control that by voice…yet.
- Turning on/off the TV is really cool. Just before Christmas I picked up a Logitech Harmony Hub on sale, and with that plus IFTTT I was able to set up a trigger phrase with a custom response to turn the TV on and off. I need to do some more work to get it all set up exactly the way I want, but right now I can say “Turn on the TV” and Home replies with “Okey dokey, artichokey” and turns everything on. It really makes me want to invest in smart lights so I can do more.
- I wish I could start casting from Google Play Music and then connect to the queue from my phone so I could see/edit the playlist. The new(ish) casting notification that comes up is a nice touch, but it doesn’t offer enough control.
- It’s funny when my kids try to use it. When Curious George finished playing yesterday Gia yelled “GOOGLE, DO MORE!” and was bummed when it didn’t respond. It’ll be rough when she learns the trigger phrases. Hopefully by that point Google adds the ability to set up profiles so it recognizes who’s speaking.
I’d love to get more and have them around the whole house…or at least add one in my office…but they’re still a little too expensive for an impulse purchase. Maybe it’s just the charm of having a new toy to play with, but now I want to do everything by voice command.
Well worth 4 minutes of your time.
Oh boy. It’s been a while…sorry. And most people who read this site probably won’t be interested in this update anyway. I’m thinking about maybe shifting focus of this to a more technical blog, and putting personal/family stuff somewhere else.
Yesterday was really frustrating for me at work. I’ve been working on automating some of our regression tests for our iOS app, and it’s just been giving me a headache. The toolset for mobile automation just isn’t nearly as mature as it is for the web…but it’s getting there.
But (and this is the entire point of this post), since all of the software I’m working with is open source I was able to read it and debug it myself. I eventually tracked it to a known issue in the WebDriverAgent (written by Facebook) that handles the actual automation on the device/simulator. Not only was it a known problem already, but the developer had a fix…but wasn’t going to be able to merge it into the baseline until after Christmas. BUT (again) since it’s all open source I was able to take his fix and manually apply it to my local copy of the software, and I’m up and running!
It’s things like this that make me so happy about working in the open source community. It’s a pretty stark difference to the world of defense contracting I left behind just over a year ago…although to be fair there are large parts of the government that are making the move over to OSS.
P.S – I mentioned a while back that I was moving over from QWERTY to Colemak. It’s been a great success so far! I’m already up to 50-60 WPM (although I was ~90 on QWERTY, so still a ways to go). But I’m writing this post from a different machine, and I’m back to QWERTY. It’s pretty painful, but the muscle memory is still mostly in place, I’m just making a lot of mistakes. So blame any typos on that.
I’m in Philadelphia for work right now…but here’s a picture of some bears.