when trying to run a fast time, I have three marathon rules:(1) never run a marathon in a season that will be historical getting warmer than cooler as time goes by (i.e. run in fall/winter, not spring/summer) March/April/May are also notoriously windy months(2) Only run marathons in the time zone you live(3) only run a marathon in a location you can get to in a 2-hour flight or 4 hour driveI understand running a race like Boston or London for the experience if you don't live there, but too many things go wrong or are less than ideal if you live/train somewhere else. Usually it's the weather and time-zone adjustment. But it could be flight cancellations, hotel f*ckups, exposure to sick people, being out of your normal daily rhythm/routine/diet/sleepI ran Boston and there were some fun energy moments witht he crowd I will always remember, but the cost of flight, hotel, food, and being surrounded by fanatics who are losing their minds and can't just relax and prepare for a race was no fun for me. People become irrational at Boston. It's just a race. I choose to run CIM, stay in a $100 a night hotel that I drive to day before and I run my race and am home watching a movie with my wife/kids by 2pm race dayI live in the Bay area and have only run CIM (which is a very fast and good weather race) save the obligatory Boston experience. 2:522:372:40 (Boston)2:322:27marathon retirement
outsiderunner wrote:
Clueless commentators saying, before the race, that it was a good day to race. A good day for a picnic, but not for a marathon. How could they not know that temperatures in the 60s and 70s are BAD for a marathon? The men's winner runs 2:12 and only one woman to break 2:30. Not a good day for a race.