I think I am onto something here. I will be taking the train 3 days a week, the commute is 40ish minutes each direction. Since there are two cycling legs in each direction, and the last leg is uphill and I’m carrying full panniers, I end up home and exhausted. If I get the laptop out on the train and work on only that project, that’s 80 minutes of work done. The train carriage has tables, and since I go against traffic, I get one to myself.

I’m having an “Ima jeenyis” moment: if I do nothing else—nothing—but come home so tired that I zone out and sleep, I got 80 minutes in. Granted, it’s not earth shattering code, but it’s required planning, problem-solving, and enough coding to make me happy. It is also a set time. No “Just one more …”. If I do that, I miss my stops. Another bonus for me is that before and after the train leg are cycling legs, when I can’t do anything but think, dream, and avoid motorized cages.

I hope as my body gets used to the new plan (What in slacker hell am I doing up at 5 and out on my bicycle at 6? And why does my bike suddenly weigh 25 tons?), I’ll be more productive at home IN ADDITION TO what I have done on the train. Right now I am spending some of my home-code time whining about my quads.

As I put 100 Days of Code to rest as I readjust my daily goals, this will keep me accountable for at least 3/7 days.