I bought a Freelap BT112 kit earlier this year. Now, I use it for almost every track workout - it’s great for getting instant feedback on every single rep. That said, I had some trouble getting my Freelap to consistently record times. Some of my initial workouts recorded less than 50% of my reps! Here are some tricks I’ve picked up to get all of my times recorded accurately:

I’m going to Idaho for the month of October! The Bay Area feels disconnected in its COVID response from the rest of the country - I’m excited to find out if that’s true.

This month, I set some huge gym PRs & ran my last time trial of the track season. With the offseason upon me, I’m ready to start a strength & explosiveness block in the weight room.

• This month, I’ve been really focused on work - we have a big launch coming very soon, so I’ve spent more hours than normal coordinating & building things for that.
• To close my track “season”, I was able to run time trials in the 100/200/400 with lifetime PRs in all of them!

• The biggest piece of news for the month: I moved out of SF into my parent’s house in Dublin! With coronavirus & related precautions, urban areas no longer have network advantages over suburbs. While Emily and I think about where we want to move long-term (perhaps Denver or New York after coronavirus fades away), we’re saving a bundle.
  • We’re really grateful to have this option: both that our jobs allow us to work remotely during coronavirus and that my parents are willing & able to house both fo us while we ride out the storm.

I’ve been working with fixed-width containers in React recently, so I’ve been able to focus on typesetting. One problem I’ve had is noticing widows in paragraph text as I change copy and styling. (widow is apparently an overloaded term in typesetting — here, I mean a single word that overflows into a new line, not a single line overflowing into a new page.) I ended up building a React component that automates widow detection - let’s dig in!