So I’ve had my Droid Incredible since Friday when I got home from work and found the FedEx truck had left it (a just-barely early 40th birthday present from Kristen; I hit my upgrade date this month).
First impressions? Incredible. The touch screen is sensitive in just the right way, easy to type and correct, select and copy text, etc., text-to-speech and speech-to-text (say a phrase into Google translator, play it back in the language of your choice), navigation, blazing fast processor and Web connection, very cool body design, feels awesome to hold, takes stellar pictures, tons of great apps. I also love the contacts integration features … sucked in all my backed up Verizon Wireless contacts and merged them with my email contacts, the contact info from my Facebook account, and then matched up my friend’s Facebook profile pics with their address cards, and they update dynamically. I don’t know why, but this pleases me a lot. I also like the WordPress app, though it’s a bit buggy. Uploaded a post a minute ago with it, along with pictures and links. Would I use it to wrong a long think piece? No. But for a quick picture with a caption? Not bad. Nice for traveling.
Downsides? This thing devours battery. You need to go find the App Killer app to shut off apps you’re not using, since they will just run in the background otherwise. And even so, you’re going to want a car charger. And maybe a spare battery…
Overall? Overall, I’ve hardly begun to scratch the surface of what this phone can do, and I’m hooked already. Glad I waited to upgrade…the early reviews from Engadget and CNET didn’t steer me wrong.
ONE WEEK LATER: Who knows how you really feel about something while you’re still in the brand new fun phase of it? Here after owning the thing for a week, I’ll add a few more quick observations that though they may be tempered by time nonetheless remain first-blush enthusiastic. The battery life issue is not as big a deal as I originally thought. It’s pretty decent for a smart phone this smart, and the Advanced Task Killer app (free) helps to minimize the drain. Going from home to work, with a charger in the car, I have no real issue with the battery. We’ll see how it does on our upcoming camping trip, though… Overall, I remain deeply impressed with the phone, but it’s no one thing about it, rather the whole package. Everything seems so cleanly and speedily to integrate, from managing multiple email accounts, Web, Google analytics for work and for my personal sites, social media accounts, contacts, files (check out the Dropbox App), photos, videos and blogging. There are some things I’d swear this phone does better and faster (maybe because it streamlines processes so much and leaves out the non-essential) than my desktop or laptop. On the other hand, there are plenty of things it still doesn’t, like making for pleasant long form reading or writing experiences. (I’m typing this update on a full sized keyboard in front of a widescreen Dell monitor. I love the phone, but not that much…)
Tags: cell phones, droid incredible
Related Posts
Volunteered at the Mount Washington Road Race yesterday… Incredible 50th anniversary race. I worked water before the race and beer after. Hard to emphasize how happy you make people when you hand them a free Tuckerman’s after they’ve just run up the tallest peak in the northeast.
Related Posts
Even as I awaited (and still await) the arrival of my back-ordered Droid Incredible (I am such geek; I can’t wait), the battery began to fail on my two-year-old LG Dare. One minute, full charge, the next minute, one bar. Then three. Then one. Then shutdown. Very annoying. Max call time shrank to about 10 minutes. The last thing I wanted to do was buy a new $40 battery from the cell phone provider, when I’m only going to have the phone a few more weeks. On the other hand, it’s been a great phone/camera/Web browser, and I was going to sell it to a friend, and didn’t want to pass it along with a trash battery. Long story short, I checked Amazon, and what was a $40 battery via the cell phone company was selling for something like $2.50 plus $5 shipping and handling. The product was OEM (original equipment manufacturer), had almost all good reviews, etc., so I figured why not give it a shot. It arrived quickly and the phone is now holding a charge the way it did back when I got it (days, even with talking, photos, video shooting, Web browsing, texting, etc.). Later talking with visiting friends, I learned they’d had a similar experience with the very expensive cables that come with A/V systems…
Tags: Amazon, battery, deals, LG Dare
Related Posts
- Open your Firefox Web browser. Open the window all the way. Go to the page you want a screenshot of.
- Hit F11 on your keyboard. This will remove all the extra file and address bar material at the top of the page so you’re just seeing the browser window.
- Hold down the “Ctrl” key on your keyboard.
- Draw the scroll wheel on your mouse toward you to shrink the overall view of the screen in your browser window until everything you want in your screenshot is visible.
- Hit the “PrntScrn” button on your keyboard.
- Paste or move your image into the graphics program of your choice.
Tags: advertising, firefox, screen capture, tools, Web browser
Related Posts
Coming into the finish. Check out the slideshow at the bottom of the post for more pictures.
So here’s the upshot on the running-another-marathon-just-six-weeks-after-Boston experiment: I had more fun running Vermont City Marathon than I’ve ever had running 26.2 miles before. The others were very high on the “satisfaction” meter: pushing yourself all out, leaving everything on the course, finishing in a white haze of exhaustion and pain, achieving a PR or a first BQ or some milestone like that. And don’t get me wrong, I ran this pretty hard (finished 3:13:06, a 7:22 pace, 137th overall, 21 of 243 in my age group), and these things always get beastly at the end, but my primary memory of this race is not going to be the pain or the finish time, but the glorious fun of this great city and the fantastic people.
The two-weeks each of recovery, back-to-peak mileage, then taper for this marathon finished rough (you can read about that here). I was still wrapping my abs with ace bandages to help deal with a bad strain on race day. In some ways I felt worn out; in others I felt pretty good. When people asked “how do you feel?” or “are you ready?” my honest answer was, “I have no idea. This could go really well, or it could be a disaster! But it’ll be fun to find out.”
Kris’ mom came out to stay at the house with the kids, and Kris and I had a romantic and nostalgic drive up to Burlington Saturday morning (I am a native Vermonter, and Kris and I lived in Barre for a year when David and Sofia were little). The road is beautiful as it winds up I89 through New Hampshire’s Lakes Region and then on up into the hills and mountains of Vermont; which were a vibrant spring green. When we got to Burlington, we checked in to our hotel and headed out to the Magic Hat Brewing Company for some samples and a bit of the factory tour.
From there we headed over to the expo, which is amazingly well put-together with lots of great vendors (and bargains) for a race of this size. This sets the pattern for all of the VCM experience: it’s run with the amenities and panache of a major big city event class marathon, without some of the hassles that come with bigger events or bigger cities. I simply cannot recommend this race and this city highly enough.
We had two groups of folks to catch up with at the expo: our NH Athletic Alliance/Stonyfield friends (through my friend Dan from NHAA, who works at Stonyfield, a couple of other NHAA runners and I were running for Stonyfield Yogurt in Oikos singlets as part of their Burlington marketing effort, which I was proud to be a part of – plug: the Oikos Greek yogurt is fabulous for building muscle, high protein, no fat, and the smoothies are killer for post race recovery), and the group from DailyMile, the running social network Kristen and I both log our training runs on. As always, it was a treat to meet in person people you’ve been sharing training tips and encouragement with online. Later we met our NHAA/Stonyfield group for dinner and a few beers on Church Street. (You know it’s a “B” race in the season when Cap’n John allows himself beer the night before! Not sure what it means that he crushed his half of the marathon relay – PR!; beer must be good pre-run carboloading fuel!) We had a drink (and got carded!) at Red Square (very cool bar, I enjoyed the locally brewed Switchback Roasted Red Ale), listening to a singer knock out old Tom Waits tunes, then a late dinner and much great conversation at RiRa Irish Pub. Back to the room by 10:30 or so.
After the race.
Wide awake at 4:30 a.m., feeling for the first time in six weeks like I might actually be physically ready to run a marathon. Strained muscles felt somehow less strained, and I felt loose and good and happy. At 6:50 a.m. we all met in the parking lot, caravanned downtown and found a parking spot about a mile from the start. Those of us running the full marathon and the first leg of the relay jogged a warmup mile to the start. I finished that with some strides by the waterfront park, brought it up a bit beyond race pace and felt good.
I won’t give a turn by turn description of the course or my race through it (who’d read such a thing?), but broadly, the course is laid out like a knot that ties the center of the city. You start by looping out three hilly city miles then come back through the center again, then out the beltway, then back through the center, then into South Burlington, then back through the center to climb the six-block hill up Battery Street at mile 16, then north again to loop back and finish along the bike path into the waterfront park. The hills, except for Battery Street, are short, and with swooping downhills and tons of corners and sharp turns, sections of the race felt like a roller coaster! And though the coaster wanted to suck me into a fast pace (6:55-7:05) I kept the regulator on and stayed at 7:15-7:20. By the time I hit mile five or six out on the beltway, I knew two things: I felt great, better than I ever would have imaged I would this close to the last marathon, but also that I wasn’t going to be running a 3:10 marathon. I’d written the major splits for that time on my arm in the car, still half thinking I might go for it, but I never really looked at them. It wasn’t the day for that milestone. I wanted to enjoy this one and that 5-7 seconds a mile difference in the pace I would have needed to push would have tipped it over the edge. (I have to say, it’s interesting to have a sense of this so early in the race, but I do think as I run more marathons that it’s entirely possible to tell how each early mile, in conjunction with how you feel during them, is going to impact the late miles.)
One of the best parts of the knot-course was that it was easy for Kristen and our other friends to see us pass not once, but three or four times. It was always such a great surprise to come around a corner or crest a hill and see her waving from the crowd. And speaking of the crowd – awesome. Burlington knows how to turn out for a race, and with the exception of a few stretches, the crowds are there cheering through the whole thing.
When I ran Boston, I was running at the far edge of my abilities and I didn’t allow myself a lot of crowd distraction; I noted the crowds but didn’t interact. I felt badly that I never hi-fived any of the kids who lined the route with their hands out (I know how much our own kids love to hi-five runners, but also how distracting that can be if somebody’s trying to focus). I made up for that during this race. I hi-fived kids all along the route. Took enthusiastically offered orange slices and freezie pops. Gave thumbs up and shouted thanks to cheers. Congratulated the 8-or-9-year-old with the bugle in one of the back neighborhoods around mile 18 on his musicianship. Cheered the many bands and drummers along the route (loved the drums, and the school band playing “Let It Snow” somewhere around mile 21, just before the bike path!). Waved to friends. Did all the things I avoiding doing in Boston because I didn’t want to use up extra energy. Somehow it seemed to bring some extra energy each time, though. You give and you get, I suppose.
I never hit the wall to pass into the hideous and grueling post-wall despair. But I did get pretty darn tired. The last five miles down the bike path along the lake felt very long (especially the first couple, with their slight uphill grade). I found my pace sagging back to 7:45 or so, and I couldn’t seem to pick it up again. I needed to shake something loose but it just wasn’t happening. The path was too straight and flat. Heaven help me, I missed the hills and corners, which helped change the muscles being used and boost my pace! I slowed to walk quickly through two water stops late race, drink carefully, and change my pace, recalibrate my muscles. This paid off – I was able to kick the 7:45 back to a 7:05 for another half a mile or so, averaging out back to my normal pace.
The crowds coming into the park were massive, loud and inspiring! I had a little kick to pick it up and ran into the park fairly fast, then negotiated the maze of twists and turns that wind through the crowd to the finish and despite getting outkicked ten feet from the finish line by another of NHAA runner (he’d started farther back in the pack, and was really more than a minute ahead of me in terms of net time, running a powerful race), I was happy with my time, and incredibly happy that I’d been able to balance a hard, if not all out, effort with some sightseeing and really enjoying the race, the city and the people. For some of our local folks, the race went tough (some do) and one of our fastest friends fell victim to awful muscle cramps after mile 16, but got up and gritted it out to the end anyway. Another ran a smoking time in the half marathon relay. And one NHAA guy, Jason Porter, won the masters division in the marathon. And for me, anyway, this race seemed like the perfect result for a “B” race, and the pleasure of it, the weekend and the course were all “A”! I will certainly be back to run Burlington again.
Tags: Boston Marathon, marathon, marathon training, vermont city marathon
Related Posts
So how do you finish 18 weeks of training, race a marathon, and then turn around and race another just as hard just 6 weeks later? I’ll tell you when and if I’ve finished the second one, this Sunday. Maybe you (or I) don’t. But I think maybe it’s possible, and here are a few observations on getting to the starting line, mostly in one piece, for the second marathon in six weeks.
First, I made it a point to say race a marathon, since I think many long distance runners could manage a 26-mile long run at an easy pace every month, or even more often than that. What requires major recovery time (about five weeks) is racing the marathon – running it as fast as you possibly can while still finishing. I ran Boston as hard as I could. I think I could have spent six weeks just recovering from that.
I wasn’t planning on trying this experiment this year. I figured after the Boston Marathon in April, I’d lay back and run easy miles for a month or two before gearing up for a fall race. But through my friend Dan from the New Hampshire Athletic Alliance running club, and who works at Stonyfield Yogurt just down the street on Londonderry, I got an opportunity to run Vermont City Marathon in Burlington on May 30 in a Stonyfield singlet as part of their marketing effort up there. I’m a big fan of Stonyfield as a company, Burlington as a city, and Vermont as my home state. This was impossible to pass up!
I basically ran two weeks of recovery mileage, with shorter distance speedwork thrown in (which I probably overdid). Then I went back to peak mileage for two weeks. This was tough. Much tougher than the five or six weeks of peak mileage I ran during the original training. I was hitting the target miles, and the target paces for my long runs, tempo runs and intervals, but I was paying for it. For once, I not only ran recovery pace runs at a real recovery pace, but even slower than that. And not by choice.
I felt like I was right on the edge of breaking down physically, and I hoped I could stay balanced there, pushing the hard workouts hard enough so I could feel confident going into this next race, but still resting enough so that I wouldn’t fall apart entirely or get injured before I got to the start line. I ate lots of yogurt (yes, Stonyfield, plug!) and almonds to try and pack in protein and good fat to rebuild damaged muscle.
By the end of the second week of peak training my legs were tired but okay, but my abs and core were deeply sore. I often get sore abs after a tough long run (not enough core workouts in between), but they go away in a day or so. Sometimes, I’ll misstep off a curb or into a pothole and wrench my abs during a tempo run and that’ll hurt for a while as well, but heal quickly. This time, the soreness got worse and worse as I stacked up hard training miles on top of a marathon, on top of more hard training miles. I began to wonder if I’d torn something.
By the time I did my last peak mileage week long run, a 16-mile hill workout, my abs were sore all the way through, and definitely cutting into my ability to run fast. I rested for two days going into taper week one, and then ran an eight-mile tempo run. I was fast again, and hit the speeds with no problem, but at mile six I landed wrong in some uneven terrain and wrench; twisted my core again so hard I winced. By the next day my belly hurt enough so I scheduled a doctor’s appointment. I didn’t think he was going to be able to fix me, but I wanted to make sure that I hadn’t torn something and didn’t have a sports hernia or something that could make running the marathon in less than two weeks not just painful, but also dangerous.
And here’s why I think our family doc is great – he’s a cyclist and athlete, and he totally gets it. After a complete exam, he told me nothing was torn. Just a bad strain, stacking up miles on miles, just as I’d thought, exacerbated by that last twist during the tempo run. But I can run, right, I wanted to know? It’s not going to do any permanent damage? ”I’ll tell you what I tell my other athletes when they come to me with an injury like this right before the last big game of the season,” he said. ”You can do it, but it’ll hurt, and you’ll pay on the other side with longer recovery time.” Nice!
I finished out the first taper week pretty well, then this past week. The last two workouts on my schedule were a five-miler today, a four tomorrow, then the marathon on Sunday. And for the first time in a long time, I bagged today’s run. My legs are feeling decent again, but my abs were still achy, and I thought, what’s this five going to do? I’m either fit or I’m not. I think a second full day of rest will do me better. Somehow this willingness to thumb my nose at my schedule pleased me. Kris’ mom is at the house to watch the kids, and she made a great dinner so at least I was able to assuage my guilt at having skipped the run (ha! not guilty at all) by carbo-loading with some herb roasted chicken and potatoes, good bread and seasoned oil, and a tasty Malbec. Strawberry shortcake for dessert. Perfect cure for whatever ails you.
So tomorrow morning an easy four miles, and then Kris and I head off to Vermont. A weekend away without the kids, touring around my home state a bit, then a race expo, early Mass, dinner, and the next day a great 26.2 mile run through a beautiful city. The run might go really well. Or not. Maybe it’ll be too hot, maybe it won’t (forecast has been all over the place). Maybe I’ll run a PR, or maybe I’ll find out that I’m even more tired and beat up than I thought I was and end up running my slowest marathon ever. I’ve got no sense of it either way (though I’m pretty sure either way I’m really going to hurt a lot on Monday); it’s all a fine and interesting experiment. I can’t wait to find out how it turns out!
Tags: Boston Marathon, marathon training, vermont city marathon
Related Posts
I see, and have to admit to using, a lot of PowerPoint in my work life. There’re things it’s good for, and some things it’s not. The Daily Show did a nice job of mocking a “things it’s not” use… Love the Star Wars moment near the end.
| The Daily Show With Jon Stewart | Mon – Thurs 11p / 10c |
| Afghanistan Stability Chart | |
Tags: PowerPoint
Related Posts
Life and work in the weeks prior to and following the Boston Marathon this year — my first Boston Marathon — were so busy I had little time, until the last few days, for the dreaded taper madness, or subsequently, to write the long, reflective blog post that’s followed my other races. That doesn’t, however mean that the running of this race was overshadowed in my mind or imagination. This was a big deal for me, and I’m deeply grateful for the opportunity to have run it. Here, almost three weeks later, are a few belated observations.
Two days before Boston I went down to the expo to pick up my number. It was a cold, gray, rainy day. And while I’ve said that I was too busy for much of the taper madness this year, I didn’t escape it entirely. The last five days or so were filled with the phantom pains and burgeoning physical and mental anxiety that accompany the sudden decrease in peak mileage. And by expo day I was fully succumbed. I plodded across the Common in the drizzle, feeling stout, bloated and puffy, achy as though I’d aged forty years in a week. All around me city runners dashed as lithe and graceful as gazelles in their youthful (even if they were old), cosmopolitan fitness. I was too resigned to my own status to even be intimidated. I was an impostor. Run a marathon? I’d be hard pressed to walk the mile to Hynes Convention Center and back. That was how I felt. But I knew some things, too. I knew what I had done in training, each tempo run, long run, speed run, recovery run. I knew I was in the best shape I’d ever been in, and if that still wasn’t what I’d hoped it would be, and if my body felt a wreck on that Saturday morning, what of it. Feelings are nice, but they’re fickle, and they succumb easily to taper madness. You train on intellect and run on will. I went on over to the expo and got my number, the whole time twisted a little with this mix of pleasant anticipation and diffident anxiety. This nervousness swelled the rest of the weekend and finally burst into delighted anticipation Sunday night. Monday morning I awoke at 4:15, before the alarm went off, and I felt ready to run.
At the expo
I remember now and assume I’ll remember 40 years from now, a great many things vividly about the day. The weather was perfect. Chilly, with blue skies and little wind. Kris drove Gary, Curt and me down, and on the way, Gary called the WZID radio station to tell the DJ how Curt was nervous because he was worried his wife Danielle might go into labor before the race was over. The DJs put the call on the air a few minutes later and made many fine jokes about this. It came up a lot throughout the morning. But the fact that people seemed a bit surprised that Curt and Danielle were both planning to be in Boston this many days past the due date, but were not greatly surprised by it, underscored how seriously folks take Boston around here.
Gary calls the radio station while Curt looks on
Kris dropped us off at one of the roadblocks in Hopkinton before heading to the T station to meet Danielle and take the train downtown. We hiked into town with hundreds of other runners, and like at all races we run in New England, we immediately ran into people we knew. People from Manchester; from our own track club even. Despite the fact that we’d not prearranged it, or that 26,000 people strong were gathering for the race. A town the size of Merrimack, New Hampshire, had turned out to run. We readied at a high school classmate’s house a few blocks from the start – she’d learned I was running Boston on Facebook and offered us a staging area. She and her husband welcome many runners into their place race morning, and it was a companionable place to finish getting one’s self together. Nice to have a couple of bathrooms free, as well. The port-a-potty lines at the athlete’s village were significant.
It’s hard to explain exactly what it was like to be in that great mass of people making its way to the starting corrals in Hopkinton. Like a massive carnival, or maybe the Carnival or Mardi Gras, or being in an army massing on a battlefield for a foot charge, or shuddering with adrenalin in the crowd just before they let the bulls free in Pamplona. Like all of those things and none of them, because this was a quintessential little New England town on a quintessential New England spring day. And as Curt and I bid Gary farewell and found our way into corral 6, right in front of the Hopkinton town hall, and the military jets screamed above us in a precision flyover, and the loudspeaker blared and the people around us threw off their sweatshirts and shook out their arms preparing to run, it felt big, but old and somehow comforting at the same time.
The gun goes off and you don’t move at first. There were about five thousand people in front of us. Then we began to walk, then pick up speed. And like one of those movies about medieval armies meeting on the field, we began to trot, then jog, then finally, just before the starting line, run. I crossed the start at somewhere around a 7:10 per mile pace and held that give or take five seconds, for the next 17 miles, through crowds as loud and exuberant and continuous as you find lining a parade route. I ran steadily and tried to hold my line and not waste energy. Though I drank in all of the sights, the crowds, the signs, the costumed characters, the storied landmarks, I didn’t swerve or high five people as I went by them. I ran my race as smartly as I could. At mile 16, I didn’t feel as though I’d started breathing hard. I felt strong and very much in control.
Shortly after mile 17, I ran into the first of the more serious hills in the race, and that and the subsequent three, took all of that strength and control and crumpled them like tissue paper. I came out of the hills struggling to hold not my planned race pace, but something much slower. The last two hills had been infinitely horrid struggles to get up and they’d cracked my pace to pieces. Down the third hill, I’d tried to come back up to my original race pace, and felt muscle spasms shoot down both legs as quads and calves protested. I slowed down ten seconds a mile and it eased. But my beyond the tight muscles, the shuddering quads, my strength was gone and my heartrate had gone through the roof. I’d come at the hills all wrong, and now I was entirely red-lined with five miles left to run. I walked through the next water stop, 15 or 20 seconds, trying to recalibrate. I ran again and was still going by people, but there were many more passing me as well, now.
I ran the last five miles in a haze of white mist and exhaustion. By the last three, I felt as though I wanted to stop every step, and that I couldn’t run a single step more. The roar of the crowd was a cacophony now, an assault, but it helped to drown out the sound of my pulse in my ears. The brief dip into the tunnel under the highway just before the end brought a few moments of blessed silence. I was tired all over my body by the time I came around the corner onto Boylston Street. Some people say that the sight of the crowd there, the finish line far down the straight, gives you a shot of adrenalin and you just sail to the finish. That didn’t happen to me. I just wondered how it could still be so far away, how I was possibly going to get across all that pavement. My arms hurt. My neck hurt so that I couldn’t turn my head without feeling as though it would cramp. I could feel my head hanging back, almost dangling on that exhausted neck. I heard Kris scream and saw her lean out of the crowd to take a picture. I tried to smile at her, but I’m afraid it may have looked like a grimace.
A brutal final stretch
That last stretch went on forever. Then I crossed the line. And stopped my watch. And stopped running. And that felt as wonderful as anything has ever felt. To stand swaying and then to walk, staggering, into that sea of volunteers to be wrapped in a space blanket and fed energy drinks and bananas and salty white potato chips. But mostly just not to be running anymore. I met Kristen, Curt (who’d finished something more than 10 minutes ahead of me) and Danielle (who’d happily not gone into labor yet) and we walked around Boston (albeit on stiff and aching legs) an hour, then took the T back to pick up the cars. We ate lunch at the Cheesecake Factory and a tall Sam Adams Noble Pils has never tasted so good.
Ahhh, celebration!
I ran Boston in 3:12:49. This was 2:49 slower than I’d hoped for, but still better than my best time, last October which was 3:13:21 at the Baystate Marathon in Lowell – my Boston Marathon Qualifying Time. Given that Baystate is flat and fast, and Boston is challenging with a miles long opening downhill stretch to tear up your quads and then a four-mile stretch from miles 17-21 with four hills to climb, thrashing your legs the other way, I felt pretty good about the improvement. In fact, I was pretty euphoric the whole way home. And for days after. I sure didn’t feel like I had something to make up for.
And I wasn’t planning on running another marathon until at least the fall. But sometimes opportunities come along that are to good to pass up. Like when a friend offers you the chance to run wearing his company’s logo at the Vermont City Marathon on May 30, and that’s just six weeks after you ran Boston. You think for a moment that prudence dictates you pass. But then you think about how wonderful the marathon is, even the awful, hurting parts, and how you’ve already gone to all the trouble of training all winter to get in marathon shape and so why not get two races in on that base, and you say, if all goes well with a six week recovery, re-training and re-tapering, maybe that 3:10 marathon is somewhere north of Boston in my old home state. Or maybe I’ll set my goal a little easier for this follow up run. Either way, still happy just to be running. See you in Burlington, friends.
If you’re looking for something to read between now and then, here’s a link to my column on marathoning that appeared in The Telegraph on Boston Marathon morning.
NOTE: Curt and Danielle’s baby was born the Friday after the marathon, and mom, dad and little Ethan Miles are all the pictures of joy and health!
Tags: Boston Marathon, marathon, Running, vermont city marathon
Related Posts
Fun video from Fast Company wherein Nike CEO Mark Parker recounts a discussion with Apple’s Steve Jobs in which he asks Jobs for advice and hears in reply: “Nike makes some of the best products in the world [...] But you also make a lot of crap. Just get rid of the crappy stuff and focus on the good stuff. Good advice for any business in which there are a lot of ideas. Edit well. (Love my Nike Air Pegasus sneaks, been through and worn out dozens (?) of pairs.)
Tags: Apple, Nike, product development
Recent Comments