I put together my 2007 season with an eye to seeing people. For IMAZ, I rendezvoused with my sister
and we visited our uncle prior. At Florida 70.3 I saw some bloggy peeps and a bunch of Toronto peeps. At IMMoo I rendezvoused with my sister, we saw many bloggy peeps, and afterward I visited folks in Wisconsin and Illinois.
The resulting structure of the season led to compromised performance at events; nonetheless I did learn some performance lessons:
o  low heart rate training below my zone 2 is not my friend;
o  my recovery from an IM is on the long side:
o  Florida 70.3 done 5 weeks after IMAZ still knocked back my trajectory;
o  I could have used another month for IMMoo prep after Florida 70.3
o  stomach may be unreliable after 13 hours:
o   should cram in more calories - more at breakfast, gel or sportsdrink before swim, and consider transition time/heart rate in starting eating on the bike;
o  muscular endurance in zone 2 was OK by IMMoo, but burned carbs and had insufficient aerobic fitness to complete much faster
o  even without proper hill training, my build can get me through; and
o  on a windy day I give up a lot of time due to my non-fully-aero position on the Poor Little Blue Cannondale (this hurts bridging rollers too).
If I want to Just Keep Running on the marathon of an IM (or go beyond that and Leave It All On The Course) I suppose I had best train and equip to go sub-13. Contrary to that requirement, although I've very much appreciated my iron-distance event days, the training hours (and to a lesser extent season design) required by a performance focus are more than I've looked to dedicate.
So, that makes three iron-distance races I've done, with two being Mdots done this season. I've used the line: "Training for an Ironman is great; actually doing one is stupid." Really, the toll on the body from the day itself *can't* be good for us. But at least it's stupid fun!