Kate Portrait

I love this portrait my sister is doing of my niece. She says it’s a work-in-progress, though I’m in favor of her keeping it in its current state.

img_5279-450.png

I can’t wait to see the companion portrait of my nephew. She paints from photographs, so I’m hoping I can provide a similar portrait of him.

Boston 2008

I’m not sure exactly why I’ve waited a month to write about Boston. Perhaps it was my almost complete lack of photo-taking. More likely, it’s the feeling that I had finally completed a major undertaking, which leaves me exhausted and satisfied for about a week, then the elation turns into nervousness as I realize that I need another goal. New goals are scary, especially considering I had five years to get comfortable with this one.

To put it simply, the Boston Marathon is the best marathon in the entire world, in practically every way. It lives up to every expectation, from the talent level of the field, the difficulty of the rolling course, to the crazy pre-race expo and festivities, to the absolutely mind-blowing crowd support.

The course is every bit as hard as people say, with a quad-crushing downhill trend for the first half, and then crushing uphills for about six miles until 22. I was a bit out of shape for a fast attempt, but I still went out a little fast, loving the opportunity to flow along with huge packs of runners my speed or faster. I honestly got a tiny bit discouraged around half-way, as I’m not accustomed to being continuously passed by entire packs of people, and this trend didn’t let up for the entire race. But even that was incredible, running in a crowd for an entire marathon.

boston2008_450.pngUncomfortably rounding one of the last corners

I’ve never seen crowd support anything like this. Honestly I wonder why so many people turn out, as they are out in decent numbers for the entire course, and in huge crowds through the towns. Children were hanging out of trees, people were barbequeing, college kids were insane. I had heard the stories of the Wellesley girls, but nothing could have prepared me for what sounded like a Beatles concert a half-mile away. I’d go back just for that.

Unfortunately I didn’t quite have the legs I had in Portland or Myrtle, and the weather turned out to be a bit hot and sunny for me, so the hills and sun took their toll on me. No mushroom clould, but running sub-3 was definitely out of the question, so I managed to hold on for a Boston-qualifying 3:13 (Note: I’ll be 35 next year, so I get five minutes, and yes, I was already qualified for ’09). Unless my dad qualifies for ’09 (he will definitely be there for ’10; more on that later), I’m going to try to kill this course next year. Revenge on those hills will be sweet.

pic-0002-edit.pngPossibly the perfect restaurant? Must try it in ’09

For the entire weekend there are runners everywhere, and you can tell they’re serious runners. Everyone wears bragging gear from previous races, or they’re already wearing a wind jacket for the current race. Thousands and thousands of people, all excited to be there. If you are a runner, really a runner, you must do Boston at least once. It’s not just the reputation, it’s a religious experience. And if you aren’t a runner, I don’t know how you could experience the Boston weekend and not be one by the end of it. Just ask Jeri, Susi, or either of the Pauls.

Happy sandboxes and svn switch

I encourage everyone I work with to keep all of their development code in a source repository, even one-off dead-end prototype code they’re not going to check back into a main development tree. If you know you’re going to do destabilizing work, of course you’ll create a sandbox branch from the development branch and then do your work; we all know this. So, what happens if you inadvertently end up with a dead-end prototype in your working source checkout, and you didn’t have the foresight to start with a branch? It’s easy to make it as if you had.

Disclaimer: Of course, if this all fails you could lose a lot of work, so you might want to generate a quick diff or backup just in case. Just be careful.

  1. Create a development branch in our repository on the server. We are using Windows and TortoiseSVN, and our working code is from the branch at svn://svnserver/MyProject/Trunk at revision 1942. So, we use the Repo-browser in TortoiseSVN to find Trunk, select revision 1942 from the upper right-hand corner of the dialog, and then select “Copy to…” with a new location at svn://svnserver/MyProject/Sandboxes/bojordan/DeadEndPrototype. We now have a new branch, but our working code still belongs to Trunk.
  2. Right-click on my top-level checkout directory, select “Switch” from the TortoiseSVN options, and select the new branch in the “To URL:”. We know HEAD is fine, as we just created the new branch.
  3. Now, the next time we commit our code, we’ll check it back into the new branch. Glee!

Just remember: No more stale development tree archives on your development machines means cleaner, uncluttered living, and might get you one step closer to a 16 minute 5k. Or, maybe not, but you’ll still be happier.