The idea is to return to the Akron Marathon in 2014. After seeing Jamoosh's post about planning a year ahead, copying him seemed like an unlikely good idea. Before I knew it, I was crafting the framework for a training plan for next year that starts now.
With a new baby at home, my focus for these remaining months of 2013 is running at least twice a week to get my legs back into some kind of groove. I'm also going to try harder to lose some of this sympathy weight. As Mrs. Viper tries to shed her own pregnancy weight gain, she has started tracking her calories, and so I'm copying her too.
By mid-November I'm hoping Baby Viper will be sturdy enough to try running with him in the stroller. Maybe by that time, we'll have decided on whether we'll enter a winter race.
Next year's plan shepherds me through winter with minimal mileage, but then begins to get more intense with slow and methodical base building in the spring, and finally concludes with an 18-week marathon training regimen that begins in the summer.
My goal is another sub-four marathon finish. Considering how little I've run these past two years and how slow my recent runs have been, my goal may be a bit ambitious. Looking at training paces, such as those found at the always unreliable McMillan Running Calculator, my easy runs should average between nine and 10 minutes per mile. That would require me to shave up to a minute and a half from my current pacing. No sweat!
Thankfully, I've never put too much stock into such rigorous calculations. Besides, even if you do it all right, the marathon can still kick you in the ass. Right, Josh?
If nothing else, it feels good to think about running with purpose again. I don't want to be stuck on the sidelines next year.
Showing posts with label marathon preparation. Show all posts
Showing posts with label marathon preparation. Show all posts
Wednesday, October 16, 2013
Wednesday, May 8, 2013
Booming Cost of Marathons
The Akron Marathon is cheap by comparison. If you wait until the expo to sign up for the event, you would pay $115, which is just a couple dollars more than the national average for marathon entry fees ($112). You can still get change for paying with a portrait of Ben Franklin until the end of this month.
With a high of 15,000 participants last year, the Akron Marathon is also pretty small. At the other end of the spectrum, there's the New York City Marathon, which will probably cost more than $250 to enter and include close to 50,000 people. So, it could be worse.
But still, $115 can pay for a lot in my world and the childish world to come. I mean, have you looked at the cost of childcare these days? Not to mention the fact that my wife needs maternity clothes; I've been wanting new strings for my fiddle; and I need some work done on my car that I keep putting off. If I had a $100 to spare right now, I wouldn't sign up for the Akron Marathon.
That seems pretty telling.
As does my reaction to reading the comments on yesterday's post along with this Esquire article, which have me thinking against the marathon this year. I love the Akron Marathon and how it ties together the city's neighborhoods. I love the community support. I love the course. But it may be time to let it go for a while.
Your comments elicited some unexpected responses. There's no way in hell I would drop $100 to sign up now and decide whether to run later. My money is always where my mouth is, and I'm a pretty quiet guy. While I could drop down to the half, there's another half marathon a month earlier that I'm considering, which wouldn't cut so close to the baby's due date.
Of course, I could just wing it. Run like I'm training and pay a premium for signing up late. In the end, this isn't life or death. It's just running. The decision can wait.
With a high of 15,000 participants last year, the Akron Marathon is also pretty small. At the other end of the spectrum, there's the New York City Marathon, which will probably cost more than $250 to enter and include close to 50,000 people. So, it could be worse.
But still, $115 can pay for a lot in my world and the childish world to come. I mean, have you looked at the cost of childcare these days? Not to mention the fact that my wife needs maternity clothes; I've been wanting new strings for my fiddle; and I need some work done on my car that I keep putting off. If I had a $100 to spare right now, I wouldn't sign up for the Akron Marathon.
That seems pretty telling.
As does my reaction to reading the comments on yesterday's post along with this Esquire article, which have me thinking against the marathon this year. I love the Akron Marathon and how it ties together the city's neighborhoods. I love the community support. I love the course. But it may be time to let it go for a while.
Your comments elicited some unexpected responses. There's no way in hell I would drop $100 to sign up now and decide whether to run later. My money is always where my mouth is, and I'm a pretty quiet guy. While I could drop down to the half, there's another half marathon a month earlier that I'm considering, which wouldn't cut so close to the baby's due date.
Of course, I could just wing it. Run like I'm training and pay a premium for signing up late. In the end, this isn't life or death. It's just running. The decision can wait.
Tuesday, May 7, 2013
To Marathon or Not to Marathon
Now that everyone knows Mrs. Viper is pregnant, they've started to ask me if I'm going to run the Akron Marathon this year.
My first concern is my wife. The race is Sept. 28, and our bundle of life change is due in the first half of October. Mrs. Viper usually watches me finish, and she will be set to pop. What if something happens while out there on the course?
My second concern is myself. I haven't run a marathon since 2011, when I set mypersonal worst married PR at 4:58:28. Since then, I haven't raced anything longer than a 10K. Last year, my wife and I joined three others in running the five-person relay at the Akron Marathon.
Right now, I should be laying down a good base for marathon training, but we all know that's not happening. While my running has picked up in recent weeks, it's nowhere near base training levels.
The thought of ramping up to 50 miles per week seems incredibly daunting. The fear of failure fills me with doubt.
There are a number of reasons why I want to run the Akron Marathon again:
My first concern is my wife. The race is Sept. 28, and our bundle of life change is due in the first half of October. Mrs. Viper usually watches me finish, and she will be set to pop. What if something happens while out there on the course?
My second concern is myself. I haven't run a marathon since 2011, when I set my
Right now, I should be laying down a good base for marathon training, but we all know that's not happening. While my running has picked up in recent weeks, it's nowhere near base training levels.
The thought of ramping up to 50 miles per week seems incredibly daunting. The fear of failure fills me with doubt.
There are a number of reasons why I want to run the Akron Marathon again:
- Marking personal milestones
- A sense of triumphant return
- Because it's a great event
But I'll need to make running a priority if it's going to happen. I don't want to sacrifice the limited time my wife and I have left as non-parents.
Taking on the marathon again may require me to do something I've never succeeded at doing: becoming a morning runner. Egads! Not that! It may be my only hope.
Thursday, September 22, 2011
Race Week: Rain, Blister
Last night's office group run provided a preview of the race day weather forecast. All day the weather alternated between torrential downpour and partly sunny skies. Of course, when we got to the bike and hike path, the clouds were in downpour mode.
Somehow I have avoided running much in the rain so far this year. Yesterday's four-miler was a nice little reminder that it can be enjoyable. However, I do worry a bit about getting cold in the later stages of the race. As mentioned yesterday, I've been rather lucky with race day weather and have never had to deal with a cool rain during a marathon.
One thing that was not enjoyable was the small blister I got on my right big toe: the first negative experience of running in the Altra Adams. Perhaps one of the Velcro straps was too tight. I'll have to see how it feels on race day. Hopefully a bandage will do the trick if the blister is still tender.
The pre-race running is more or less done. I'm planning a couple of easy two-milers today and tomorrow to stay loose. I'm looking forward to the expo tomorrow. While I doubt I'll buy anything, I enjoy seeing the wares for sale and feeling the buzz from the crowd.
My final duty before the race, however, is finding a suitable post-race beverage. Good thing today is "growler Thursday." Cheers!
Somehow I have avoided running much in the rain so far this year. Yesterday's four-miler was a nice little reminder that it can be enjoyable. However, I do worry a bit about getting cold in the later stages of the race. As mentioned yesterday, I've been rather lucky with race day weather and have never had to deal with a cool rain during a marathon.
One thing that was not enjoyable was the small blister I got on my right big toe: the first negative experience of running in the Altra Adams. Perhaps one of the Velcro straps was too tight. I'll have to see how it feels on race day. Hopefully a bandage will do the trick if the blister is still tender.
The pre-race running is more or less done. I'm planning a couple of easy two-milers today and tomorrow to stay loose. I'm looking forward to the expo tomorrow. While I doubt I'll buy anything, I enjoy seeing the wares for sale and feeling the buzz from the crowd.
My final duty before the race, however, is finding a suitable post-race beverage. Good thing today is "growler Thursday." Cheers!
Wednesday, September 21, 2011
Race Week: My Humps My Humps My Humps
Here we are, midweek of Race Week, and the weather forecast has proved to be a flip-flopper. Remember when I said it will be completely different than it was last week, when Weather.com called for low 60s and rain on Race Day? My forecast was proven correct just a couple days later, when that same website predicted mid-60s and sunshine for the Akron Marathon. Today, we're back to low 60s and rain.
I've been rather lucky without dealing with such Race Day humps as bad weather. My marathons have been especially fortuitous without so much as a scattering of rain drops. Last year, I was expecting showers and even created a trashbag rain slicker, but the rain never arrived. Luckily, I still have that modified trashbag to use this year.
Yesterday, after reading a tale of two barefoot marathon wins, I had the thought, 'You know, cluck it, maybe I should just run the marathon without shoes.' Granted, my longest barefoot run this year was five miles and my longest ever was 10 miles, but this is the year if ever there was a year when I could focus on taking it slow. First, there was taper sickness and now the madness.
Of course, I haven't practiced at all running barefoot on the Towpath, which makes up a three-mile stretch from about miles 11 to 14. If you remember last year's race, I picked up a pebble in my shoe during this stretch, which forced me to stop and lose my pace group. The crushed limestone surface of the Towpath is anything but smooth and would require some serious focus to run it barefoot.
As I considered this option, I decided to make it a goal next year to get comfortable running barefoot on the Towpath and similar terrains. For this year's race, though, I'll stick to shoes, my new Altra Adams.
Packet pickup is Friday. And then one last hump to traverse.
I've been rather lucky without dealing with such Race Day humps as bad weather. My marathons have been especially fortuitous without so much as a scattering of rain drops. Last year, I was expecting showers and even created a trashbag rain slicker, but the rain never arrived. Luckily, I still have that modified trashbag to use this year.
Yesterday, after reading a tale of two barefoot marathon wins, I had the thought, 'You know, cluck it, maybe I should just run the marathon without shoes.' Granted, my longest barefoot run this year was five miles and my longest ever was 10 miles, but this is the year if ever there was a year when I could focus on taking it slow. First, there was taper sickness and now the madness.
Of course, I haven't practiced at all running barefoot on the Towpath, which makes up a three-mile stretch from about miles 11 to 14. If you remember last year's race, I picked up a pebble in my shoe during this stretch, which forced me to stop and lose my pace group. The crushed limestone surface of the Towpath is anything but smooth and would require some serious focus to run it barefoot.
As I considered this option, I decided to make it a goal next year to get comfortable running barefoot on the Towpath and similar terrains. For this year's race, though, I'll stick to shoes, my new Altra Adams.
Packet pickup is Friday. And then one last hump to traverse.
Tuesday, September 20, 2011
Race Week: Dog Days
Fighting off the sickness is daily challenge. The change in weather and my bride's full submission to the cold/flu/allergies/creeping crud has made for some iffy mornings. Thankfully, by mid-morning, my immune system seems to bat down the icky-ickies.
Still two runs left to complete before the race. One of them was supposed to be today. Evening plans forced me to consider a morning run today, but reality resulted in that not happening. No matter. Tomorrow will be fine.
And since there's not much to report on the running side of life. Here's a recent photo of our dog, Dobson, who just got this new toy.
Upon first playing with his newest item of spoilage, he nearly ran into the wall, the coffee table, the door jamb, the couch, and the lamp. Good thing he's cute.
Still two runs left to complete before the race. One of them was supposed to be today. Evening plans forced me to consider a morning run today, but reality resulted in that not happening. No matter. Tomorrow will be fine.
And since there's not much to report on the running side of life. Here's a recent photo of our dog, Dobson, who just got this new toy.
 |
| Dobson likes his new toy, but he doesn't see what's so funny. |
Monday, September 19, 2011
Race Week: Taper Sickness
This morning, my throat was a bit sore, my mind felt as if it were encased in gauze, and my body seemed stuck in sludge. After killing my final long run on Friday and a short but invigorating run last night, my immune system suddenly feels susceptible to sickness. This is why tapering is stupid.
Last week was my highest mileage total of this training cycle thanks to my delayed 20-miler. Despite a strong 36 miles logged, my final Parrott Prediction forecasts an uninspiring 5:09:17. However, my legs feel fresh and my head is in the right place (i.e., no, not up my rear end).
Regardless of my finish time this Saturday, I'm focusing on a strong finish. That's all I really want. When I pass my throng of spectators at the end, I want them to think, "Wow, he's looking good."
My eight-miler last week on the Buckeye Trail made me believe I can run strong. Flying though the woods and down the ravines and across the streams and up the hills, I made like Natty Bumppo on the hunt.
My feet were quick and my balance was true. Except for a near faceplant when my Altra Adams slipped their grip and my left arm caught me just in time but then felt numb from the jolt for a few minutes afterward, I was a champion trail runner.
Then, after a rest day, a fast barefoot run around the neighborhoods instilled further confidence that my legs would be ready come race day.
I have two more runs this week: a six-miler tomorrow and then an easy two-miler Thursday. If I can avoid the sickness, which the Enthusiast is suffering more from than I am today, everything will be fine. The first step is getting to the starting line healthy.
Last week was my highest mileage total of this training cycle thanks to my delayed 20-miler. Despite a strong 36 miles logged, my final Parrott Prediction forecasts an uninspiring 5:09:17. However, my legs feel fresh and my head is in the right place (i.e., no, not up my rear end).
Regardless of my finish time this Saturday, I'm focusing on a strong finish. That's all I really want. When I pass my throng of spectators at the end, I want them to think, "Wow, he's looking good."
My eight-miler last week on the Buckeye Trail made me believe I can run strong. Flying though the woods and down the ravines and across the streams and up the hills, I made like Natty Bumppo on the hunt.
My feet were quick and my balance was true. Except for a near faceplant when my Altra Adams slipped their grip and my left arm caught me just in time but then felt numb from the jolt for a few minutes afterward, I was a champion trail runner.
Then, after a rest day, a fast barefoot run around the neighborhoods instilled further confidence that my legs would be ready come race day.
I have two more runs this week: a six-miler tomorrow and then an easy two-miler Thursday. If I can avoid the sickness, which the Enthusiast is suffering more from than I am today, everything will be fine. The first step is getting to the starting line healthy.
Friday, September 16, 2011
Flashback Friday: Eight Days a Week Redux
We're on the home stretch now. Everything is in place, including the recycled blog title, with just eight days to complete four more runs before the Akron Marathon, including an eight-miler tonight.
Thankfully, nothing should intrude on these final runs. The schedule is more or less clear for the next week. Although it's too late to make any major improvements to my fitness, running is at long last the main focus.
I'll take this remaining time to work, not on the actual miles, but the mentality of running a marathon while severely undertrained. The weather forecast has improved and, if correct, will go a long way in making race day more enjoyable, with a high in the upper 60s and sunshine.
This year is all about racing for the fun of running. Being well as opposed to doing well. Running with the community rather than running against it.
Finding joy in my performance must come from a different source. The final number I see above me at the finish line won't be inspiring, but knowing that I gave my best with the least training I've ever had entering a marathon will provide some solace.
Back Talk
Wherein my fellow married readers help pump up my ego
Barefoot Josh knows where the real accomplishment resides: "A successful wedding is a way bigger accomplishment than just about anything achievable in the running world. Re marathon, you know what to do. You'll be fine. Enjoy!"
Answer: Unless my wedding band cuts off my circulation and my finger falls off.
Jamoosh reminds me that a PR is in my forecast after all: "Regardless, it will be a 'Married' PR!"
Answer: As I've been told, a PR is a PR, lost finger or not.
Happy Hour is nearly upon us, teammates. Have a finely brewed weekend. Run well and drink well. Cheers!
Thankfully, nothing should intrude on these final runs. The schedule is more or less clear for the next week. Although it's too late to make any major improvements to my fitness, running is at long last the main focus.
I'll take this remaining time to work, not on the actual miles, but the mentality of running a marathon while severely undertrained. The weather forecast has improved and, if correct, will go a long way in making race day more enjoyable, with a high in the upper 60s and sunshine.
This year is all about racing for the fun of running. Being well as opposed to doing well. Running with the community rather than running against it.
Finding joy in my performance must come from a different source. The final number I see above me at the finish line won't be inspiring, but knowing that I gave my best with the least training I've ever had entering a marathon will provide some solace.
Back Talk
Wherein my fellow married readers help pump up my ego
Barefoot Josh knows where the real accomplishment resides: "A successful wedding is a way bigger accomplishment than just about anything achievable in the running world. Re marathon, you know what to do. You'll be fine. Enjoy!"
Answer: Unless my wedding band cuts off my circulation and my finger falls off.
Jamoosh reminds me that a PR is in my forecast after all: "Regardless, it will be a 'Married' PR!"
Answer: As I've been told, a PR is a PR, lost finger or not.
Happy Hour is nearly upon us, teammates. Have a finely brewed weekend. Run well and drink well. Cheers!
Thursday, September 15, 2011
Looking Beyond the Marathon
My running has been off kilter all year--until now. Despite missing some runs last week, my mojo seems to have returned after my last long run on the Buckeye Trail, which was also my first run in the Altra Adams. Had I a few more weeks to get ready for the Akron Marathon, I believe I could make a real push for a PR. But, as my high school art teacher always said of missed opportunities, "Shoulda, woulda, coulda."
With the weather cooling, running is becoming more enjoyable. Heat and humidity aren't oppressing the miles like a lead blanket. My legs feel pretty fresh, and I'm looking forward to the running for the remainder of the year.
The Enthusiast asked me the other day how I'd feel about running a short run with her soon. Fall is when my new bride gets interested again in running. We're planning a three-mile run Sunday, as I wind down my taper for the marathon.
My training cycle has done at least one thing well, and that is getting me motivated to run more. However, I have nothing beyond the Saturday after next. I'd like to say I will run just for the enjoyment of running for the next few months, but I know better. Training keeps me motivated.
This year I've added quite a bit more trail running to my routine. Many of my longer runs have been conducted on the Buckeye Trail or within the trail systems of the Cuyahoga Valley National Park and the Summit County Metro Parks. However, despite my increased activity on these more technical terrains, I have yet to run a trail race.
During last night's group run, one of my coworkers mentioned the Salt Fork 10 Mile Trail Challenge, Dec. 3, in Cambridge, Ohio, just east of Columbus. Everything I read about trail races leads me to believe that the events cater more to my kind of people. For instance, like other trail events, the Salt Fork race gives finishers a pint glass.
There is also my continued efforts to become more skilled as a barefoot runner. Going shoeless has taken a bit of a back seat since receiving my new shoes, as I am trying to break them in for the marathon, which is now just nine days away.
The point is that the Akron Marathon won't be the end of the running season for me this year. There are plenty of miles yet covered and plenty of time left to run them.
With the weather cooling, running is becoming more enjoyable. Heat and humidity aren't oppressing the miles like a lead blanket. My legs feel pretty fresh, and I'm looking forward to the running for the remainder of the year.
The Enthusiast asked me the other day how I'd feel about running a short run with her soon. Fall is when my new bride gets interested again in running. We're planning a three-mile run Sunday, as I wind down my taper for the marathon.
My training cycle has done at least one thing well, and that is getting me motivated to run more. However, I have nothing beyond the Saturday after next. I'd like to say I will run just for the enjoyment of running for the next few months, but I know better. Training keeps me motivated.
This year I've added quite a bit more trail running to my routine. Many of my longer runs have been conducted on the Buckeye Trail or within the trail systems of the Cuyahoga Valley National Park and the Summit County Metro Parks. However, despite my increased activity on these more technical terrains, I have yet to run a trail race.
During last night's group run, one of my coworkers mentioned the Salt Fork 10 Mile Trail Challenge, Dec. 3, in Cambridge, Ohio, just east of Columbus. Everything I read about trail races leads me to believe that the events cater more to my kind of people. For instance, like other trail events, the Salt Fork race gives finishers a pint glass.
There is also my continued efforts to become more skilled as a barefoot runner. Going shoeless has taken a bit of a back seat since receiving my new shoes, as I am trying to break them in for the marathon, which is now just nine days away.
The point is that the Akron Marathon won't be the end of the running season for me this year. There are plenty of miles yet covered and plenty of time left to run them.
Wednesday, September 14, 2011
Ten-Day Forecast
We are 10 days away from the Akron Marathon. My only 20-miler is in the books. My strategy is more or less set. My shoes have been chosen. And my short taper has begun.
The weather forecast, which likely will be completely different on race day, calls for high-60s to mid-70s and rain on Sept. 24. Until then, I will run every other day in a stepped mileage pattern. Thus, I will run four miles today, eight miles Friday, three miles Saturday, six miles Tuesday, and two miles the following Thursday, before running the big 26.2 miles on the Saturday after next.
Now that the main running is out of the way, my mind can start focusing on potential finish times. So let's crunch the numbers!
My last Parrott-derived time was 4:50:53. McMillan gives me a 4:38:11, based on my Buckeye Half Marathon results. And today, I arrived at yet another possible predictor: my average pace differential from each year's half marathon and marathon results.
Here's what I did: Going back to 2007, I took the average pace from my marathon performance and subtracted the most recent half marathon average pace of that same year to arrive at a pace differential. Because I ran two marathons in 2008, I arrived at five pace differentials.
I removed the highest and lowest differentials, because the highest was a clear bonk at the 2008 Akron Marathon, considering I set a PR two weeks later at the Towpath Marathon, and the lowest was when I decided to purposefully run slow at the 2009 Buckeye Half Marathon to test a pacing strategy for that year's Akron Marathon.
With the resulting three pace differentials, I have averaged an increase of 1:23 in average pace from my half marathon to marathon performances each year. Therefore, if I averaged 10:04 per mile at this year's Buckeye Half Marathon, this new predictor would indicate an 11:27 mile pace at the Akron Marathon, a finish of 4:59:59. Good thing I don't advocate a five-hour cutoff time for marathons!
All along, I have said 4:30 would be an "A goal" for this year's race, considering my limited training. Now I'm backing off that pipe dream as well. Nothing in my training suggests I could approach anything close to a 10:18 pace for a marathon.
Dating back to June, my monthly average pace has been no faster than 10:53 per mile for long runs, which might predict a 4:45:09 marathon finish. However, last month's average mile pace was 11:22, for a possible 4:57:48 marathon time.
The reality is that there is no steadfast predictor of your potential marathon performance. So much can happen over the course of 26.2 miles that it's impossible to determine how your race will unfold on any given day.
I just have to relax and accept chaos as truth. Anything can happen, and that's the mystique and allure of running marathons.
The weather forecast, which likely will be completely different on race day, calls for high-60s to mid-70s and rain on Sept. 24. Until then, I will run every other day in a stepped mileage pattern. Thus, I will run four miles today, eight miles Friday, three miles Saturday, six miles Tuesday, and two miles the following Thursday, before running the big 26.2 miles on the Saturday after next.
Now that the main running is out of the way, my mind can start focusing on potential finish times. So let's crunch the numbers!
My last Parrott-derived time was 4:50:53. McMillan gives me a 4:38:11, based on my Buckeye Half Marathon results. And today, I arrived at yet another possible predictor: my average pace differential from each year's half marathon and marathon results.
Here's what I did: Going back to 2007, I took the average pace from my marathon performance and subtracted the most recent half marathon average pace of that same year to arrive at a pace differential. Because I ran two marathons in 2008, I arrived at five pace differentials.
I removed the highest and lowest differentials, because the highest was a clear bonk at the 2008 Akron Marathon, considering I set a PR two weeks later at the Towpath Marathon, and the lowest was when I decided to purposefully run slow at the 2009 Buckeye Half Marathon to test a pacing strategy for that year's Akron Marathon.
With the resulting three pace differentials, I have averaged an increase of 1:23 in average pace from my half marathon to marathon performances each year. Therefore, if I averaged 10:04 per mile at this year's Buckeye Half Marathon, this new predictor would indicate an 11:27 mile pace at the Akron Marathon, a finish of 4:59:59. Good thing I don't advocate a five-hour cutoff time for marathons!
All along, I have said 4:30 would be an "A goal" for this year's race, considering my limited training. Now I'm backing off that pipe dream as well. Nothing in my training suggests I could approach anything close to a 10:18 pace for a marathon.
Dating back to June, my monthly average pace has been no faster than 10:53 per mile for long runs, which might predict a 4:45:09 marathon finish. However, last month's average mile pace was 11:22, for a possible 4:57:48 marathon time.
The reality is that there is no steadfast predictor of your potential marathon performance. So much can happen over the course of 26.2 miles that it's impossible to determine how your race will unfold on any given day.
I just have to relax and accept chaos as truth. Anything can happen, and that's the mystique and allure of running marathons.
Thursday, September 1, 2011
From the Back
My strategy for the Buckeye Half Marathon was by design to follow the nonexistent 2:15 pace group, but by happenstance I was also at the back of the pack. I eventually finished in 2:11, but I wonder what my time would have been had the race been truly chip timed.
The Buckeye has recently started using chips to record finishing times, but there is no starting mat to cross, which makes it just a glorified gun time. And that's fine. There were less than 500 racers between the individual runners and relay teams. It's not like you were waiting several minutes to cross the starting line, as will be the case at the Akron Marathon.
Martini PR'd at the Cincinnati Flying Pig Marathon by running from the back and spending most of his time catching up to the 4:00 pace group. Not that I'll have that kind of speed, but the same strategy may help me stay slow at the beginning miles and avoid blowing up later in the race.
September arrives with just nine days before the wedding and 23 days until the marathon. My final two long runs await, and then it's a short taper before the race. Here is last month's statistical rundown:
- Total Miles: 105 miles (16 runs)
- Total Time: 18:21:35
- Highest Weekly: 32 miles
- Average Weekly: 26.25 miles
- Average Pace: 10:29.48 (improvement!)
- The Monthly Dif: +46 miles (59 miles in July)
August takes over as my biggest month of running. I've gotten quite a bit faster since July, but I'm troubled by the amount of runs that have been in shoes.
Only 27.6 percent of my mileage (24 miles) last month was done barefoot, whereas the rest of my runs were either in racing flats (19 miles), trail shoes (18 miles), or my new Invisible Shoes (43 miles). The Vibram KSOs (4 miles) got banned.
Although my barefoot mileage is greatly increased from last year, my conversion to the shoeless craft has not been as "whole hog" as I had planned. Granted, I was purposefully putting more miles in the huarache sandals for my review.
While I've more than doubled the percentage of shodless miles from last year, the total is nowhere near the majority of my running. Having run 378 miles so far this year, the breakdown goes like this: New Balance 101s at 33.8 percent (128 miles), bare feet at 22.2 percent (84 miles), Vibram KSOs at 22.2 percent (84 miles), Invisible Shoes at 11.3 percent (43 miles), and Brooks T6 Racers at 9.2 percent (35 miles). And soon, there'll be another shoe to add to the mix.
Only 27.6 percent of my mileage (24 miles) last month was done barefoot, whereas the rest of my runs were either in racing flats (19 miles), trail shoes (18 miles), or my new Invisible Shoes (43 miles). The Vibram KSOs (4 miles) got banned.
Although my barefoot mileage is greatly increased from last year, my conversion to the shoeless craft has not been as "whole hog" as I had planned. Granted, I was purposefully putting more miles in the huarache sandals for my review.
While I've more than doubled the percentage of shodless miles from last year, the total is nowhere near the majority of my running. Having run 378 miles so far this year, the breakdown goes like this: New Balance 101s at 33.8 percent (128 miles), bare feet at 22.2 percent (84 miles), Vibram KSOs at 22.2 percent (84 miles), Invisible Shoes at 11.3 percent (43 miles), and Brooks T6 Racers at 9.2 percent (35 miles). And soon, there'll be another shoe to add to the mix.
Wednesday, August 31, 2011
Battle of the Predictions
As you know, I've been testing the George Parrott marathon prediction theory. However, I've also always loved playing with the McMillan Running Calculator. For the Buckeye Half Marathon, I plugged my Parrott predictions into the McMillan site to arrive at my goal finish time and pacing parameters.
With the Akron Marathon just a few weeks away, I'm trying to formulate a pacing strategy, using the two prediction systems as a basis. Problem is they're giving me mixed signals.
Last week's Parrott prediction, which includes my race and the brutal run home from work, gave me a marathon finish time of 4:50:53, my slowest forecast yet.
With my Buckeye time as a base, McMillan predicts a finish of 4:38:11, paradoxically my fastest forecasted race time.
And all along, I've set 4:30 as my A-plus goal.
This feels similar to my first marathon, when my goal was 4:00 and I finished with a 4:26, only add a half hour. Of course, I can't rely on the past week's runs as my sole criteria for guessing my race finish time. I still have two more big training weeks ahead, with an 18-miler this weekend and my only 20-miler next week.
I might as well add some more predictions to the mix. When do you think I'll finish the Akron Marathon?
With the Akron Marathon just a few weeks away, I'm trying to formulate a pacing strategy, using the two prediction systems as a basis. Problem is they're giving me mixed signals.
Last week's Parrott prediction, which includes my race and the brutal run home from work, gave me a marathon finish time of 4:50:53, my slowest forecast yet.
With my Buckeye time as a base, McMillan predicts a finish of 4:38:11, paradoxically my fastest forecasted race time.
And all along, I've set 4:30 as my A-plus goal.
This feels similar to my first marathon, when my goal was 4:00 and I finished with a 4:26, only add a half hour. Of course, I can't rely on the past week's runs as my sole criteria for guessing my race finish time. I still have two more big training weeks ahead, with an 18-miler this weekend and my only 20-miler next week.
I might as well add some more predictions to the mix. When do you think I'll finish the Akron Marathon?
Wednesday, August 17, 2011
Testing the Parrott Predictor
I've never heard of George Parrott other than through the Excel-based running log I've been using for the last several years. And that log was put together by some other guy I've never heard of, named David Hayes. And that log isn't easily found to download, as far as I can see, so this probably makes no sense to you--unless you use the same running log I do.
But anyway, my running log has a page called "Parrott Predictor," which is based on this George Parrott's idea and is supposed to be able to predict your marathon time based on your actual training paces.
According to Hayes' spreadsheet, "George Parrott, known affectionately as 'Coach George' on the Dead Runners Society listserve, presented this idea a couple of years ago. He suggests that a runner can run no faster in the Marathon than he runs his fastest 26.2 miles in a week during training. Calculating what miles are the fastest, adding them up until you get to 26.2, then adding all the times associated with those runs can be tedious. Thanks to ideas contributed by Dale Shoup of DRS, this worksheet does it for you."
No, I don't know anything about the Dead Runners Society, but the only live link I've found to Hayes' spreadsheet is at the DRS website. Running Times magazine had a review of the free running log back in 2005, and there's a Runner's World discussion thread about the aforementioned Parrott Predictor and how bogus it is.
However, that won't stop me from testing its accuracy. Last week, I logged just enough miles to get my first prediction: 4:41:48. I've been saying that 4:30 is my "A goal" for the Akron Marathon, so it seems I have a little catching up to do to quicken my pace from 10:50 to 10:18 per mile.
Last year, my best prediction was 4:01:35, and I ran a 3:58:46 PR. But that was chip time; my gun time was 4:02:10--just 35 seconds slower than the Parrott Prediction. Going back to 2009, my best prediction was 3:51:18, and I was way over that with 4:04:47.
But remember, the description says I can run "no faster" than my fastest 26.2 miles during a training week. If I stick to gun time, which is the true clock time after all, the Parrott Predictor works. For the next, gulp, six weeks (really?!?) I'll be reporting my Parrot Prediction score. Hopefully, we'll see trend toward faster times. At the very least, it will give you a gauge to predict my failure on race day.
But anyway, my running log has a page called "Parrott Predictor," which is based on this George Parrott's idea and is supposed to be able to predict your marathon time based on your actual training paces.
According to Hayes' spreadsheet, "George Parrott, known affectionately as 'Coach George' on the Dead Runners Society listserve, presented this idea a couple of years ago. He suggests that a runner can run no faster in the Marathon than he runs his fastest 26.2 miles in a week during training. Calculating what miles are the fastest, adding them up until you get to 26.2, then adding all the times associated with those runs can be tedious. Thanks to ideas contributed by Dale Shoup of DRS, this worksheet does it for you."
No, I don't know anything about the Dead Runners Society, but the only live link I've found to Hayes' spreadsheet is at the DRS website. Running Times magazine had a review of the free running log back in 2005, and there's a Runner's World discussion thread about the aforementioned Parrott Predictor and how bogus it is.
However, that won't stop me from testing its accuracy. Last week, I logged just enough miles to get my first prediction: 4:41:48. I've been saying that 4:30 is my "A goal" for the Akron Marathon, so it seems I have a little catching up to do to quicken my pace from 10:50 to 10:18 per mile.
Last year, my best prediction was 4:01:35, and I ran a 3:58:46 PR. But that was chip time; my gun time was 4:02:10--just 35 seconds slower than the Parrott Prediction. Going back to 2009, my best prediction was 3:51:18, and I was way over that with 4:04:47.
But remember, the description says I can run "no faster" than my fastest 26.2 miles during a training week. If I stick to gun time, which is the true clock time after all, the Parrott Predictor works. For the next, gulp, six weeks (really?!?) I'll be reporting my Parrot Prediction score. Hopefully, we'll see trend toward faster times. At the very least, it will give you a gauge to predict my failure on race day.
Monday, August 15, 2011
Everybody Plays a Fool Sometimes
So far during this marathon training cycle, I have maintained an ultraconservative ramp up in weekly mileage, increasing distance by 10 percent or less. This past weekend held a 12-miler in store for me, as I would strive for 26 miles total. But then I ran with the Martini, and everything changed.
We got together Saturday morning for my long run, which required me switching my planned five-miler to Sunday. However, Martini's trail route would rearrange my plans.
This was the first time in a long time that I ran with Martini this year. He's been busy running multiple marathons and an ultra, while I have busy not doing those things. For Saturday's run, he took me on part of the Fools 50K course, which he ran in April and finished well under 6:30.
Martini claimed the run would be about 12 miles, linking together a variety of trail loops in northern Summit County. With the aggressive trails, I wore my New Balance MT101s, a low-heeled but stiff-soled shoe.
I carried with me a bottle of watered down Gatorade (orange G2) with chia seeds. It was the first time I have carried any sort of hydration or food during a run this year.
The morning temperatures were cool for the start, but it definitely warmed up by the end. Martini tracked the run with a GPS app on his phone, and the little electronic voice kept ticking off the mileage.
By the time we reached the last trail loop, we were already over 10 miles. I was starting to realize this run was going to be longer than planned. Everything felt fine up until that point, but I was already beyond my longest run of the year, which I logged last Monday.
We had been running at about 11 to 12 minutes per mile, a slower pace than most of my long runs this year but faster than most of my trail runs to date.
Martini's phone announced 11 miles, and my legs started to feel cramped.
I started trying to gauge how much farther we had to go, and the sound of 12 miles didn't make me feel hopeful.
I was just hanging onto the pace when I heard 13 miles, but I started to recognize the end was near -- one way or another.
Finally, we emerged from the woods to the rolling grassy hills of Pine Hollow. The final tally was just over 13 and a quarter miles, our final pace just under 12 minutes per mile.
The five miles I had planned for Sunday became four.
We got together Saturday morning for my long run, which required me switching my planned five-miler to Sunday. However, Martini's trail route would rearrange my plans.
This was the first time in a long time that I ran with Martini this year. He's been busy running multiple marathons and an ultra, while I have busy not doing those things. For Saturday's run, he took me on part of the Fools 50K course, which he ran in April and finished well under 6:30.
Martini claimed the run would be about 12 miles, linking together a variety of trail loops in northern Summit County. With the aggressive trails, I wore my New Balance MT101s, a low-heeled but stiff-soled shoe.
I carried with me a bottle of watered down Gatorade (orange G2) with chia seeds. It was the first time I have carried any sort of hydration or food during a run this year.
The morning temperatures were cool for the start, but it definitely warmed up by the end. Martini tracked the run with a GPS app on his phone, and the little electronic voice kept ticking off the mileage.
By the time we reached the last trail loop, we were already over 10 miles. I was starting to realize this run was going to be longer than planned. Everything felt fine up until that point, but I was already beyond my longest run of the year, which I logged last Monday.
We had been running at about 11 to 12 minutes per mile, a slower pace than most of my long runs this year but faster than most of my trail runs to date.
Martini's phone announced 11 miles, and my legs started to feel cramped.
I started trying to gauge how much farther we had to go, and the sound of 12 miles didn't make me feel hopeful.
I was just hanging onto the pace when I heard 13 miles, but I started to recognize the end was near -- one way or another.
Finally, we emerged from the woods to the rolling grassy hills of Pine Hollow. The final tally was just over 13 and a quarter miles, our final pace just under 12 minutes per mile.
The five miles I had planned for Sunday became four.
Friday, September 24, 2010
Flashback Friday: One
One day to go, and I am of one mind for the marathon tomorrow. I'm as ready as I'll ever be. I've rounded up most of my race-day supplies, but I still need a couple items, which I'll look for today at the Akron Marathon expo.
The most important item I purchased last night was my finisher's prize, a 64-ounce growler of Ommegang Chocolate Indulgence.
My not-really-local-at-all Whole Foods store (Cedar Center) started selling growlers this month, and I've been eager to check it out. You can use any clean, 64-ounce growler or buy theirs for $3.99. They have a small, but interesting selection of brews on tap, which will rotate periodically.
I haven't had any Ommegang in quite some time. The Chocolate Indulgence is a seasonal brew with a dark and heavy body and a bold and rich flavor, which should serve as plenty of motivation to finish strong.
I just hope I don't veer off course when the route passes near my apartment ...
Back Talk
Wherein there were many good comments this week to address.
Jamoosh speaks up about his race-day supply list: "What's on my 'must have' list for race day? An awesome pit crew so I don't have to carry/stow anything!"
Answer: The bottle and gel will be gone within the first six miles. My gear bag will be transported to the finish line for me, so this isn't an inconvenience.
BrianFlash also has some input about racing necessities: "No water bottles, gels or food, etc. I figure the race is supported so they have what I need. ... By the way -- watch sucking down those painkillers. They aren't particularly good for you while running."
Answer: Yes there will be water and gels supplied on the course, but I like to skip the first water stop because it's usually too crowded, and the first gel station isn't until after 10 miles, which is a bit too late for me. The pain killers are for after I finish.
SunRunner sent me on a wild goose hunt for additional gear needs: "I know it sounds lame, but get a pair of diabetic compression socks at your local MegaMart or CVS to wear after the race. They're only $5 or so and they accomplish the same purpose as the fancy-ass $45 ones you can find at the running stores. ... I know you're a cheapskate, so I figured the $5 price tag might tempt you to crack open that dusty wallet of yours."
Answer: Well, you're right. Your fanciful tale did tempt me to crack open my desiccated billfold, but I call bullshit on that five-dollar holler. I found compression socks all right, but at three times your price. However, the Enthusiast talked me off the ledge and convinced me to buy them anyway. So, thank you?
21-Day Jess suggested one more item I should pack for after the race: "I NEED a pair of sandals or flip flops after a race. The first thing I want to get off and get rid of are my shoes."
Answer: Good call. I added that to my list, but how will they look with knee-high black compression socks?
Spike was curious about what my other personalities had planned for the marathon: "What about PostMarathonSuperDrunkViper? What about his strategy?"
Answer: His strategy is to walk from the starting line to the finish and start imbibing, skipping the race altogether.
Andrew couldn't care less that there were four days left until the marathon; he was more interested in my dog's name: "How did you pick the name Dobson?"
Answer: As somewhat alluded to in this post, Dobson is the surname of a banjo builder from the late 1800s and early 1900s. Henry C. Dobson patented in 1881 the first banjo tone ring, which helps amplify the sound. Here is what one of those Dobson banjos looks like. When the Enthusiast said she wanted an Old English Sheepdog, I told her to save her pennies like I was doing at the time for my banjo, which is considered a Dobson-style banjo because it has a reproduction of that tone ring. And now you know way more than you ever wanted to about banjos.
Thank you to all you who have offered your advice and encouragement throughout my training for this race. I will make you proud.
Happy Hour is nearly uponus those of you not on the wagon. Have a finely brewed weekend. Good luck to my fellow racers. Run well and drink well. Cheers!
The most important item I purchased last night was my finisher's prize, a 64-ounce growler of Ommegang Chocolate Indulgence.
My not-really-local-at-all Whole Foods store (Cedar Center) started selling growlers this month, and I've been eager to check it out. You can use any clean, 64-ounce growler or buy theirs for $3.99. They have a small, but interesting selection of brews on tap, which will rotate periodically.
I haven't had any Ommegang in quite some time. The Chocolate Indulgence is a seasonal brew with a dark and heavy body and a bold and rich flavor, which should serve as plenty of motivation to finish strong.
 |
| 64 ounces of YUM! |
Back Talk
Wherein there were many good comments this week to address.
Jamoosh speaks up about his race-day supply list: "What's on my 'must have' list for race day? An awesome pit crew so I don't have to carry/stow anything!"
Answer: The bottle and gel will be gone within the first six miles. My gear bag will be transported to the finish line for me, so this isn't an inconvenience.
BrianFlash also has some input about racing necessities: "No water bottles, gels or food, etc. I figure the race is supported so they have what I need. ... By the way -- watch sucking down those painkillers. They aren't particularly good for you while running."
Answer: Yes there will be water and gels supplied on the course, but I like to skip the first water stop because it's usually too crowded, and the first gel station isn't until after 10 miles, which is a bit too late for me. The pain killers are for after I finish.
SunRunner sent me on a wild goose hunt for additional gear needs: "I know it sounds lame, but get a pair of diabetic compression socks at your local MegaMart or CVS to wear after the race. They're only $5 or so and they accomplish the same purpose as the fancy-ass $45 ones you can find at the running stores. ... I know you're a cheapskate, so I figured the $5 price tag might tempt you to crack open that dusty wallet of yours."
Answer: Well, you're right. Your fanciful tale did tempt me to crack open my desiccated billfold, but I call bullshit on that five-dollar holler. I found compression socks all right, but at three times your price. However, the Enthusiast talked me off the ledge and convinced me to buy them anyway. So, thank you?
21-Day Jess suggested one more item I should pack for after the race: "I NEED a pair of sandals or flip flops after a race. The first thing I want to get off and get rid of are my shoes."
Answer: Good call. I added that to my list, but how will they look with knee-high black compression socks?
Spike was curious about what my other personalities had planned for the marathon: "What about PostMarathonSuperDrunkViper? What about his strategy?"
Answer: His strategy is to walk from the starting line to the finish and start imbibing, skipping the race altogether.
Andrew couldn't care less that there were four days left until the marathon; he was more interested in my dog's name: "How did you pick the name Dobson?"
Answer: As somewhat alluded to in this post, Dobson is the surname of a banjo builder from the late 1800s and early 1900s. Henry C. Dobson patented in 1881 the first banjo tone ring, which helps amplify the sound. Here is what one of those Dobson banjos looks like. When the Enthusiast said she wanted an Old English Sheepdog, I told her to save her pennies like I was doing at the time for my banjo, which is considered a Dobson-style banjo because it has a reproduction of that tone ring. And now you know way more than you ever wanted to about banjos.
Thank you to all you who have offered your advice and encouragement throughout my training for this race. I will make you proud.
Happy Hour is nearly upon
Thursday, September 23, 2010
Akron Marathon Countdown: Terrible Twos
My reverse taper is complete. My brisk four-miler last night, wearing my huaraches, put me at nine miles for the week. After the marathon, my mileage this week will be higher than last week (12 miles), which was higher than the week before (six miles). Let's not let my multiple personalities see this.
With two days until the Akron Marathon, my focus is off running and now all about preparing my body for the Saturday's fun run: eating right, hydrating, abstaining from delicious adult beverages, and getting my beauty rest. Today is the crucial day for loading up on carbohydrates and taking in my fluids. If you wait until the day before, you've waited too long.
In addition to paying attention to my nutritional needs, today is also when I put together my race gear: what to wear, what to carry, and what stow in my gear bag for after the race.
Wearing:
- Brooks T6 Racers (658 miles)
- Reebok shorts, black
- New Balance shirt, bright fucking yellow
- Timex Ironman watch
Carrying:
- Water bottle
- Throwaway layer
- One energy gel
Stowing:
- Cell phone
- Recovery beverage(s)
- Towel
- Fresh shirt
- Pain killers
What's on your must-have list for race day?
Wednesday, September 22, 2010
Akron Marathon Countdown: The 3
The many faces of the Viper are in full view as three days remain until the Akron Marathon. Evenkeel Viper is prevailing over the Freakout and Ubermensch Vipers. However, I'll need all three of them to pull it together on race day.
Freakout Viper got me out the door Monday for my last hard run Monday. Ubermensch Viper told me how awesome I was during that run. Freakout Viper returned the next morning when I felt a bit sore from the effort. Ubermensch Viper took satisfaction in the pain. Today Evenkeel Viper is the calm before the storm. Here is where the strategy emerges.
Evenkeel Viper must be pragmatic, a cold and calculating runner who knows how to bring out his best performance on race day. Saturday's weather forecast appears to be favorable with a high of 63 degrees and mostly sunny skies. It's time to put together a plan for the race.
Freakout Viper knows how tough it has been to break four hours. My race tends to break down in the park sections of the race from the Towpath through Sand Run. Evenkeel Viper knows that strength comes in numbers. I will run with the four-hour pace group until I've cleared this hurdle and only then will I attempt to pull ahead with a negative split strategy, which is Ubermensch Viper's favorite path to awesomeness.
So there you have it. Nothing fancy. Just a straightahead plan to beat four hours. But Evenkeel Viper reminds me that the time isn't the ultimate goal. The No. 1 goal is to have fun. Having fun relaxes you. Being relaxed is integral to good running form. With good form comes speed. I'm ready to run my best no matter what the final score reads.
Tuesday, September 21, 2010
Akron Marathon Countdown: Four!
My legs exuded the satisfying dull ache from a good run when I woke up this morning. Last night's final tuneup before the Akron Marathon lasted almost an hour. I left my watch at home and improvised my route.
No time, no distance.
With four days left before the marathon, I wanted a tough run without the pressure of meeting a timed goal. I ran down the long descent of Portage Path to Sand Run Parkway and then turned onto a par course trail that took me up the hill on a steeper path, meandering over to Merriman Road for the run back home.
That's what the Akron Marathon does to you, wrecks your quadriceps on a steep downhill and then attacks your hamstrings and calves as you slowly climb out of the Cuyahoga River valley.
I ignored the taper pains in my right groin. I will feel pain during the marathon. I will have to manage the discomfort like I did last night, by keeping my running fourm in check.
I've been thinking a lot about my goals four this race. I've been consumed with my time goal. But is that the most important aspect of running the Akron Marathon? Four is the magic number. Four days to go. Four hours -- hopefully less than -- of running. Therefour, four goals:
- Have fun
- Focus on good fourm
- Feed off the crowd (spectators, other runners)
- Break four hours
I'm putting the time goal last, as it is appropriately fourth on my list. My first priority is to enjoy the run, soak in the great crowd support, feel the camaraderie of my fellow racers, and don't get discouraged if it's not my day. While I have a time goal, I want to reduce the pressure of a time goal. Race times are not the reason I run.
Happy Birthday
Dobson the wonder puppy is a year old today. Happy birthday buddy. The Enthusiast and I got him when he was three months old. He effectively ended my stretching routine. He got his own beer. And he's provided endless joy ... with a tiny bit of frustration mixed in for good measure.
Here he is enjoying the view along the Towpath. Yes, he got a haircut. Old news that went unreported.
Monday, September 20, 2010
Akron Marathon Countdown: Race Week
Five days, people, we have five days until the Akron Marathon and my bid to break four hours. My weekend plans were a success, and I'm now on the dreaded wagon until after the race.
Last week produced another sad tale of lackluster running. Let's hope I haven't done too little in the last couple weeks. I'm hoping to get in one last hard workout today and regain my mojo before the big day. This self-inflicted drama will make for some much needed suspense around these parts.
Until I succumbed to my own variety of taper madness -- which has exhibited itself as plain old procrastination -- my training has been rather uneventful. The runs were scratched off one by one, resulting in my highest training mileage to date and a new personal best in the half marathon, as planned.
Can I regather my motivation and capture a little lightning in a bottle this Saturday? Stay tuned!
Friday, September 17, 2010
Flashback Friday: Crazy Eights
We're down to eight days until the Akron Marathon. I'm starting to get the "taper pains." You get those, right? Mysterious pains that appear out of nowhere?
Ow, my hip!
Ooch, my knee!
Ooph, my toe!
These little aches can't be the result of running, because I have done very little of that lately. Last night, I was all excited to run what I planned to be my last double-digit mileage before the race, a 12-miler on the back half of the marathon course. Then a landlocked hurricane swept through Akron and doused those fiery urges.
This weekend, I'll have my last binge of food and beverage. Tonight, the Enthusiast and I are headed to a Greek festival for dinner (and probably some ouzo) and then to Cleveland to listen to some Old Time and imbibe a bit of beer to help open up the ears to the music. Tomorrow, we're headed to Ohio's wine country. But before that, I'll be getting my wig busted to make myself more aerodynamic for next Saturday's main event.
Back Talk
Wherein we embrace absurdity.
The Enthusiast knows how to motivate me: "How about a relaxing post-race beer bath of Baltika, Zane Lamprey style? I would seriously do it for you -- if you come in under 4."
Answer: It's been a while since I've been Baltika'd. That would be most recuperative!
Ian has the most absurd suggestion of the first nine comments for yesterday's post: "I like Sun Runner's suggestion of 9 beers after the race, perhaps while watching the Browns rush for 9 touchdowns."
Answer: Wait a whole day to drink? Are you nuts? The race is Saturday, and I'll need more than nine beers in me before the Browns play. And sadly for your fantasy team, the Browns will probably bench Jerome "The Ghost" Harrison after he fails to run for 300 yards against Kansas City for the second straight year.
Happy Hour is nearly upon us, teammates. Have a finely brewed weekend. Run well and drink well. Cheers!
Subscribe to:
Posts (Atom)