Vacation (aka Cross-Training)

Stefanie and I at Breckenridge.

This past week I was on vacation.  It was a vacation from work and my typical running schedule, but it actually turned out to be a pretty big week of training, all things considered.  You see, I'm not really a lay-on-the-beach-for-a-week vacation kinda guy.  I like to be doing stuff.  And one of my favorite things to do is go skiing - or snowboarding to be specific.

The uphill view from our condo.

A sweet deal on a friend's condo led us to Silverthorne, CO which is close to the ski resorts of Breckenridge and Keystone.  It's also happily situated 8,700 ft above sea level.  The ski resorts themselves just go up in elevation from that point.  I've been skiing several times before, but it's been a long time since I've stayed that this kind of elevation for any length of time.  And I don't remember running at this altitude either.   Let me just say that it was tough running at elevation.  It didn't help that our condo was located on a mountainside where my only options were to run up or down.  And if I chose down, well, then I had to finish going back up.

Stefanie and I, joined by our old friend Matt, were scheduled to arrive at our destination around 4:30pm on Sunday.  A tractor-trailer accident resulting in a closed interstate made for an interesting detour through a snowy Loveland Pass and a 7pm actual arrival time.  Our 1.5 hr drive was turned into a 4 hr drive.  Not fun.  And I still had to run.   Seven miles on the dark, snowy roads.  You'll find that 7 miles is a common theme.  That's how many miles I ran every day that I was in Silverthorne.  I guess it's an arbitrary choice, but 50 mpw is sort of my self-imposed minimum mileage.  I find it's best just to pick 7 miles a day and not give myself an option, because motivation to get out and run is pretty low while on vacation even for a running nut like myself.  Plus, I knew that I'd probably be able to run more Saturday and Sunday following the weekdays of skiing.

Monday morning I got up and put in my 7 miles before heading to the slopes.  I averaged around 7:30 pace for most all of my runs during the week, but it felt more like 6:30 effort - or faster.  Tuesday, same thing, I ran before skiing.  Most of the time, when I'm traveling with or visiting others, I try to get up and run in the morning before things get going.  I find that reduces the chance that I will get stuck doing something in the afternoon/evening that might interfere with my run.  But I don't particularly like running in the morning.  The slopes closed at 4pm which left me with plenty of daylight, so I switched over to running in the afternoon on Wednesday.

Me all geared up with Peak 8 in the background.

When you're snowboarding from 9am to 4pm, the legs tend to be a little tired for the run in the afternoon.  So it would only make sense on Wednesday, knowing I still had to run in the evening, that I would take the ski lift as high as it would go and then proceed to hike the rest of the way to the summit of Peak 8 at 12,998 ft.  If the skiing itself wasn't cross-training enough - climbing at 13,000 ft, in snowboarding boots, through soft powder snow, with the wind trying to blow you off the mountain - now that is serious cross-training.  It was only about 150 vertical feet of climb, but I had to stop several times to rest.  When I finally reached the summit, I was sucking wind like I'd just run an all-out mile.  It was so much fun that I repeated the challenge on Friday in even windier conditions.

The convoy of all the other crazies hiking to the summit.

On top of the world.

Double black diamond - the only way down from here.

I continued running my easy 7 miles in the evening on Wednesday, Thursday and Friday, but Thursday's run is worth noting.  I ran 2 miles up the mountain from our condo to a snow-covered trail.  I carried my YakTrax and slipped them on just before I hit the trail.  The snow was packed down by previous trail users and the YakTrax gripped beautifully.  It was really a treat to run through a forest blanketed in white.  I even encountered some cross-country skiers and quickly passed them.  I was so excited that I clocked a 5:10 for the final downhill mile on the road back to the condo.

The Saturday we wrapped up our vacation and were leaving Colorado presented a unique opportunity for me.  It's a long story, but there turned out to be a 5 hour gap between Stef's flight out of Denver and mine.  I decided to take this opportunity to go run on the Magnolia Road that I've read so much about.  After dropping Stef and Matt off at the Denver airport, I drove an hour to a spot just west of Boulder.  I continued driving up a paved, windy mountain road until the pavement ended.  This is where 'Mags' begins.  A 7.5 mile long dirt road, just above 8000 ft in elevation where many great runners have logged countless miles.  I parked on a small pull-off and began running with my camera.  I never run with a camera.  The road is rolling and climbs a manageable 400 ft from the start to the turn-around.  But the elevation is killer for a guy used to sea-level running.  For the 15 mile roundtrip, I averaged a measly 7:15 pace while running at 6 min/mi effort.  A long week of skiing could account for some of my fatigue, but the legs really felt decent.  I was hurting for oxygen though.  That was a very weird feeling.  I guess I expected to feel that way in Silverthorne.  But, here, on the road where the Colorado cross-country team trains, I expected to be able to run closer to a normal training pace.  I didn't fully appreciate the brutal effect the elevation has on this run.  Mags is beautiful in its own way, and I encourage any runner who has some time in the Boulder area to seek it out and experience Magnolia Road for yourself.

Enough warning signs for you?  Don't start running here.  Drive up 4.5 miles
to where the pavement ends and the dirt begins.  You'll be glad you did.

Magnolia Rd with snow-capped mountians in the background.

Magnolia Rd elevation profile.

Prior to arriving in Colorado on Sunday, I spent Friday and Saturday in San Diego for a college friend's wedding.  The weather was absolutely perfect for running, and I wondered aloud on Facebook why I was choosing to spend the majority of my vacation in Colorado as opposed to staying in San Diego.  After my week in Colorado though, I know I made the right decision.  I loved every minute in Colorado.  And although I wore more clothes, I was strangely never cold while running.  Obviously, I love skiing enough that I would sacrifice a week of optimized training just a month out from the USATF 100k to hit the Rockies.  I also can see why so many of the top trail ultra guys love Colorado enough to make it their home.

Last time down the mountain for my girl.

Singles

I normally consider my "running week" to be Monday to Sunday and log my miles accordingly.  But this week I am going to do something a bit different and tell you about my Thursday to Wednesday week of running.  Why?  Well, last week I spent Monday-Wednesday recovering from the Sylamore 50k, and this Friday I leave for a week of vacation.  So the front end of last week and the back end of this week are going to be boring.  And let's just be honest here, what I did in middle makes me look way cooler.

Before I get to the details, I think this would be a good opportunity to share one of the key features of my personal training plan.  I want to use my blog to occasionally share some of my training philosophies, and I felt it was important when looking at my past 7 days of training to understand the distinction of running this kind of mileage in singles as opposed to padding the mileage log with what I consider to be "junk" doubles.

Singles.  By my definition, singles simply mean a single run per day.  Now, depending on my audience here, you might ask, "What other kind of training philosophy is there besides running once per day?"  It's actually quite common for collegiate and elite post-collegiate distance runners to run more than once in a 24 hour period to boost their mileage.  You may have heard runners talking about doing "doubles" - and that's exactly what they were referring to - running twice in one day.  From my experience, it seems serious runners start considering double runs at around 70 miles per week. 

While my weekly mileage is consistently over 70 mpw, I almost always get my mileage in on just 7 runs per week.  This is largely a personal decision, but one I find works well for me, especially when considering the time constraints imposed by a full-time career. 

A typical double would be a 5-8 mile easy run in the morning or evening, depending on when you do your primary workout, and could happen just one day a week up to six days per week for really advanced professionals.  The purpose of a double is that allows you to increase your mileage with less stress on the body than the same amount of mileage in singles.  It's logical that two 5 mile runs, with 10 hours of rest in between, are less demanding on the body than one 10 mile run.  But, you also get less training adaptation from those two 5-milers than you would from the single 10-miler (assuming you can stay injury-free).  And your total time spent on the double preparing, running, and showering afterward takes up more total time out of your day than it would for the one 10 mile run.  There is something to be said about an easy second run "flushing out" the legs and aiding recovery, but that hasn't proven to be all that helpful to me personally.

For me, waking up at 5:30 AM to be out the door and running at 5:45 usually means I'm extremely tight and still half asleep.  I would do more than half of my run at 8 min/mi pace (1:15 slower than my average recovery pace) just trying to warm up my muscles to a normal functional ability.  I believe I get more benefit out of a single 12 miler at 6:45 pace, than a 6 mile/9 mile double.  And maybe the worst thing to me is that the double would come at the expense of about an hour of precious sleep.  I believe proper sleep is one of the most overlooked aspects of a complete training plan, and I know I don't get as much as I should even running just once a day.

  

[Disclaimer: Everyone is different and what works for me may not work for you.  If you aren't over 60 miles a week on singles, don't even think about doing doubles yet.  I also spent many years gradually building my strength up to the point where I could run 100 mpw in singles.  Lastly, I'm training for 50k's and 100k's, not 5k's and 10k's.]

If you're still reading, you probably want to know what I did last Thursday to Wednesday that would cause me to get out my soapbox, so here goes: 

Thursday:  9 mi @5:40 pace on the treadmill

                 with 3 mi warmup and 1 mi cooldown for 13 mi total

Friday:      Easy 12 mi in 79 min (6:40 pace)

Saturday:  25 mi in 3 hrs, 

                (7 mi road warmup, 14 mi tough/muddy little trail race, 4 mi road cool down)

Sunday:    15 mi really easy in 1:44 (6:56 pace)

Monday:   12 mi easy in 82 min (6:50 pace)

Tuesday:   Track workout: 2 mi warmup, strides & drills, 

                2x2mi w/2min recovery (10:38, 10:33)

                + 6 mi on the roads in 35:30 (5:55 pace), 1 mi cooldown. 

Wednesday: 12 mi in 81 min (6:45 pace)

Weekly Total: 102 miles in singles (average 6:42 pace)

That's a pretty gnarly week of training for me.  Good thing next week is vacation and a down week. I need it now.  I can tell that level of training is right at the limit of what my body can handle.  Let's hope it wasn't too much.

Results from Saturday's race - Frosty 14 Trail Race.
Some good pictures from Frosty 14 - I'm on pages 1 and 13.

Yeah, He's Just That Kinda Guy

Sylamore 50k race report
2/19/2011

The conversation went something like this:

Dink: You made your travel plans for Sylamore yet?
Me: Not yet, are you coming?
Dink: Yeah, I told you I would.
Me: Yeah, but I know you had to find someone to volunteer for you at Black Warrior 50k so I wasn't sure.
Dink: It's taken care of.
Me: You registered for the race yet?
Dink: Registered?  I'm not running.  I'm coming to crew for you.
Me: What? Are you serious?  When I asked if you wanted to come, I expected you would race as well.

So let me get this straight.  Dink Taylor, the man who set the course record at the Sylamore 50k 11 years ago, was going to spend a weekend away from his family, drive 8 hours to the middle of nowhere Arkansas, solely for the purpose of crewing for a guy that was trying to break his course record and pocket the $2000 prize for doing so.  Yeah, he's just that kinda guy.

The conversation really started over a year ago.  Dink told me about his 3:40:37 course record at Sylamore that he ran in 2000.  Now the race director was putting up $2000 for someone who could break that mark.  Dink figured somebody would eventually break the record, so why not have it be me?  At least that's the story I heard.  I was running pretty well last year, coming off a 2:26 marathon at Rocket City and building my 50k trail resume, so I thought sure, I'd give it a shot.  Dink really talked the course down as well.  He made it seem as if it would be no problem for me.  When I thought about Dink's 2:40 road marathon PR compared to my 2:26, I figured that even on a tough course I'd have enough speed cushion to break his mark.

I was wrong.  I ran 3:48 last year after being reduced to walking a substantial portion of the last 6 miles.  Even though I still was able to win the race, I was demoralized.  I still feel today like I was capable of running faster than his mark last year, but I just made several errors that ultimately led to my implosion. 

The day before last year's race, I ran to the infamous creek crossing just a mile into the race.  I crossed the creek to check out the trail on the other side and quickly realized that this was anything but the easy course that Dink and the pictures on the race website made it out to be.  This year I knew what I was getting into. 

After moving to Cincinnati last summer, I didn't really plan on racing Sylamore in 2011 just for logistical reasons.  But the race haunted me.  And the closer we got to 2011 the more I started to think about it.  It wasn't really about the money or the course record anymore.  It was more me vs Sylamore.  It defeated me last year, and I wanted my revenge.  With some new-found confidence from my great race a Mtn Mist a few weeks ago, it was decided.  I was ready to battle.

I wish I had an interesting story about the actual race itself to share - but I really don't.  I took the lead after watching eventual 2nd place finisher Ben Creehan end up in the creek with water up to his neck.  I hit the trail and never looked back.  The first 6 mile section is surprisingly technical.  It's just too rocky to go very fast.  The next five miles is more runable but there's also a decent amount of climb to make things tough.  It's an out-and-back style course and I hit the turnaround in 1:48.  Pretty close to what I did last year and two minutes under CR pace.  But what I did next was very different than last year.  As opposed to trying to bury my competition at mile 16, I was patient and focused on running relaxed.  Pretty soon I started encountering the other runners on their way to the turnaround point.  They all seemed to know that I was chasing the course record and virtually everyone shouted words of encouragement.  At the next aid station my split indicated that I was another minute ahead of CR pace.  If it ain't broke don't fix it.  So I kept running relaxed and tried not to push.  I started encountering more groups of runners now and most of them were very considerate and moved aside to let me pass.  I only ran into one girl.  She stepped out of line suddenly to pass some folks and I was coming quick in the other lane.  I caught her shoulder pretty good, but I don't think she fell down.  Sorry about that and I hope you're ok. 

Despite my efforts to run relaxed, passing people and hearing more words of encouragement caused me to continue easing down on the accelerator.  Soon, I was passing participants in the 25k race that started an hour after the 50k.  I don't care if you're passing people running 12 min pace in a completely different race, it's a mental boost to pass someone.  Well, at least this year it was.  Last year these people were annoying obstacles.  This year they were cheering fans.  It's amazing what a powerful effect your mindset has on your physical performance.

I cleared the final aid station confident that I'd be able to hold it together.  In 2010, right on CR pace at this point, I made the fatal error of skipping the last aid station.  My water bottle nearly empty, body dehydrated and my legs out of fuel, I quickly bonked and struggled through the last 6 miles.  This year, I got my pacing right.  I got my nutrition right.  The trail was uncharacteristically dry and fast.  The weather was nothing to complain about.   It all came together.  With a little more than a mile to go, I crashed back into the creek crossing like I was sprinting from the beach into the ocean.  A group of spectators cheered as I ran through the water and exited on the far bank.  I killed the last bit of dirt and paved roads to the finish.  3:31:44.  A sub 1:44 return trip negative split.

It wasn't magical like Mtn Mist 3 weeks ago.  Despite my efforts to run controlled for most of the race, it hurt.  That course is tough.  I requires a unique combination of speed for the flat sections, strength for the numerous climbs and the ability to run technical trails very well.  It just never quits.  It doesn't have the show-stopping climbs of the Mist or the brief sections of extremely technical trail, so you have to be able to run everything - and fast if you want the course record.  I realize Garmin's don't do elevation very well, but mine recorded 4,500' of climb - 1,000' more than Mtn Mist.

When people look at Dink's 3:40 from 11 years ago, they usually overlook what he did immediately following that race.  The May 2000 issue of UltraRunning magazine reported:

In a twelve-day period, he ran the Sylamore Trail 50-km in 3:40, breaking the course record by 15 minutes. The next week, he ran the Mount Mitchell Challenge 40 Mile in 4:57, breaking the course record by 45 minutes. Then he broke the course record [at the Mississippi 50 mile] by 27 minutes.

Of course, Dink didn't tell me about his unbelievable hot streak until after the race last year.  Dink considers that string of races some of the strongest racing of his career.

I am hugely in debt to Dink for unselfishly suggesting the race and then coming out and crewing for me this year.  That was a crucial piece of the puzzle that I missed last year and allowed me to get my nutrition without stopping at the aid stations.

Yeah, he's just that kinda guy.  But you probably knew that already.

Epilogue:
I always like to reflect on lessons learned after my races.  Sitting in O'Hare airport at 9pm Sunday night, with terrible weather in Chicago, waiting for my delayed flight and looking at a 1AM arrival into Cincinnati, the biggest lesson I learned this weekend was this: Don't wait too long to purchase your airline tickets and, if possible, get a direct flight.  I failed miserably on both accounts this trip.  I made it home at 3AM - 12 hours after Dink dropped me off at the Memphis airport.

Additional race coverage and reports:
http://www.sylamore50k.com/ViewResults.aspx?year=2011
http://endurancebuzz.com/2011/02/24/sylamore-trail-run-2011-results/
http://morehorsethanrider.blogspot.com/2011/02/sylamore-50k.html
http://mtntrailrunner.blogspot.com/2011/02/sylamore-50k-out-to-fast.html

Beat

Week of Feb. 7, 2011: 97 miles (6:53 pace)

Sylamore 50k creek crossing at miles 1.5 and 29.5.

This was a big week.  Tuesday's track session turned into an unexpectedly good, but intense workout.  I usually meet up with the Earth Drummers team - a competitive distance running team that is supported by Bob Roncker's Running Spot - for this quality run.  I typically do the marathon group's scheduled workout, sometimes modifying it for my personal goals.  I occasionally will have someone to run with, but lately I have been mostly doing these workouts alone after the team warmup, strides, and drills.  I feel like my road marathon speed is a big differentiator between myself and some of the other top ultra guys in the country right now - and I'd like to keep it that way.  Sometimes it feels odd to not have complete control of your running schedule when you are self-coached, but I don't really believe in magic workouts.  Should I do 3x2mi or 6x1mi this week?  I don't think it matters as much as some people might think as long as you're doing the workout at the correct pace.  I find that trading some control for being able to enjoy the camaraderie and encouragement of the team pushes me to do workouts that I know I wouldn't have the motivation to do if I were running on my own.

This week was 1x2mi (10:28) + 3x1mi (5:11, 5:12, 5:07) + 2x800m (2:32, 2:26) + 2x200m (way too fast).  Everything except the 200s was followed by a 400m jog recovery.  The temperatures were in the teens and the wind wasn't exactly calm, but I really felt quite good.  I couldn't believe the splits I was hitting for the 2 mi considering how relaxed I was running.  Maybe my legs were so numb that I couldn't feel the pain.  Or maybe I'm just a good cold weather runner.  Cold weather definitely doesn't seem to detract from my performance, and I'm pretty sure I run better when it's sub-freezing than when it's 70 deg+ and humid.  Anyway, that was as fast as I've gone in a long time, and I really wasn't planning on busting out anything like that, it just happened.  My legs hurt that night (mostly from the 200s), but surprisingly, I felt OK on Wednesday.

I took it easy Wednesday and Thursday before trying a hill workout on the treadmill Friday.  It was 2x2mi at 8% grade and 6:49 min/mi pace with 1 mi recovery at 7min pace in between climbs.  That comes out to about 1700 ft of climb in 5 miles if you include the recovery mile...at sub 7 min pace.  It was tough, especially mentally.  I had never done a treadmill hill workout before, and it's hard not being able to focus on the crest of a hill.  The hill just keeps going. 

Saturday I hit the trails at Mt Airy forest and did two loops of the Stone Steps 50k course in 2:15 (17 mi).  The snow had been packed down and re-frozen on the trail, so it was still pretty slippery even though the daytime temps were getting into the 40s.  Descending some icy trail stairs and unable to stop, I slipped and fell hard on my back with my head snapping down against the ice.  I laid there stunned for a minute, but it appeared I had no major injuries as a result.  My neck may have suffered the most from the incident as it is still sore today from what feels like a muscle strain.  After running a 70 min first loop, I completed the 2nd in just 65 min, which was pretty tough considering the trail conditions.  Probably a little harder than I should have gone.

Sunday was scheduled to be a long, slow 25 mile run on the roads.  Just time on my feet.  Temps in the 50s were nice, but it was also really windy, which wasn't nice.  The week's workload was finally catching up to me as I never felt very good.  I find that I have trouble running slow though.  I would have been happy starting with 7 min pace working toward 6:45 pace at the end, but I was already averaging sub 6:45 at mile 4.  Even though my legs felt like trash, I just stuck to 6:40 and kept moving.  I found myself losing motivation around mile 18, so I found someone to chase and threw in a 6:08 mile to catch him.  I was able to ride that little boost and get myself close enough to home to finish the run respectably.  2:45 total for 6:36 pace overall.  Wish I could have slowed down and felt better, but it doesn't seem to buy me much.  I need to figure that out before I attempt a 100-miler or I'm in trouble. 

Overall, a great week of training.  Most mileage I've done since October and the quality was impressive as well.  I'm tired for sure.  Now it's time to rest up so I can take a shot at the course record at Sylamore this weekend.

Miles, Mountains, and Meatheads

Week of Jan. 31, 2011: 86 miles (6:37 pace)

Big thanks to The North Face for sending me this pair of Single-Tracks.
I'll post a review after I've run in them a few weeks.

Over a week out from Mountain Mist and feeling recovered, it was time to start working hard again.  On Tuesday, with rain falling and temps in the 30s, I decided to hit a local gym for a treadmill workout.  I did 5x1mi w/3min jog recovery starting at 5:30 pace and working it down to 5:18 for the last one.  I was pretty cautious with my pace because I have done very few hard workouts on a treadmill.  It felt like I was running fast, but I wasn't that tired afterward and probably would have gone faster if I were on a track.  On the other hand, my recovery periods on the treadmill never dropped below 7 min pace.  That probably would not have been the case if I had run faster miles on the track.

Following easy days on Wednesday and Thursday, I headed to my favorite hill repeat spot on Friday.  As best I can figure, this road climbs just shy of 300 ft in 3/4 of a mile.  I summited five times and I usually try to keep the pace brisk on the way back down each time.  My last two climbs were the fastest right around 4:45.  I felt a bit stale at first, but loosened up nicely.   I kept a running clock on the entire workout and ran 13.5 miles total in 1:28 (6:49 pace).  I'm pretty happy that I was able to maintain a relatively fast pace for the whole run considering all of the elevation change.

But that's not the "mountain" mentioned in the post title.  On Saturday, Stefanie and I had a chance to check out the Perfect North ski area which is located in Indiana, about 45 min from our house.  This "mountain" boasts 400 ft of vertical and 100 acres of skiable terrain.  We got a great group rate and thought it would be a good warmup for our big Colorado ski trip next month.  Skiing (technically snowboarding in my case) is maybe one of the only activities that I allow to interfere with my running.  It's just one of the few things in life that I enjoy enough to sacrifice my training occasionally.  I was going to run a bit in the morning before skiing, but it was 34 deg and raining when I woke up, so I vetoed that plan.  We skied from 10AM to 5:30PM, drove home, then I ran.  I only went 9 miles, which is pretty short for a run on the weekend, but I actually felt decent.  The legs were tired for sure, but they didn't seem to be running tired.

I thought Sunday's long run might be compromised as well because of sore and tired legs, but the ski trip seemed to have little negative effect.  I tried to start really relaxed and worked into things as I determined the legs felt fine.  I went 22.5 miles in 2:26 and I averaged just under 6 min pace the last two miles.  I am very pleased to have been able to run my long run at that pace considering the hill repeats on Friday and skiing on Saturday.  It was a very good week of running for me.

Meatheads.  I ran Tuesday's workout at a local gym because Stefanie had recently joined and had some free guest passes.  Part of her new membership included a fitness assessment with the head of the gym's personal training department.  When asked about her typical workout, Stefanie told him that she normally did 45 min to an hour of running or spinning.  The trainer then proceeded to tell her that was too much cardio and her body would start to consume her muscles for energy if she did that much aerobic work.  He then asked, "Have you ever seen the body of a marathon runner?"  She was pretty fed up with this guy by now and uncharacteristically came back with the sharp response of, "Actually, my husband is a professional ultramarathon runner."  Obviously surprised, he gathered himself and clumsily continued on explaining the finer points of a marathoner's lack of muscle mass.  "You can see all their ribs."  He of course attributed that fact to my body burning my muscle as energy.

I know it's possible for your body break down muscle protein for use as energy.  But, my understanding is that only occurs in extreme situations.  And I know my muscles are compact as a direct result of my endurance training (and genetics), but I'm fairly certain it's not because my body has used them to serve my energy requirements.  Unfortunately, I've had trouble finding much reputable research on the subject.  Namely, when does your body start to break down your muscles to use as an energy supply?  If anyone out there has the answer to this question or some links to related information, I'd appreciate you sharing.

The trainer also told her that marathoners don't live very long.  True story.


Edit Posted 2/7/11:

Here's a source that confirms what we already knew...from Lore of Running by Tim Noakes, MD:

"Protein is used as an energy source during exercise, and only under extreme conditions, such as complete starvation or prolonged exercise lasting three for more hours (especially under conditions of carbohydrate depletion), does its contribution reach even 10% of the total energy production (P.W.R. Lemon and Mullin 1980)."

"Most elite runners are genetically programmed to have a small muscle bulk, which increases little, if at all, in response to weight training programs.  This most likely reflects a reduced capacity of their muscles to respond  to the muscle-building (anabolic) properties of the male hormone, testosterone."

I think we can officially call this myth busted!  My muscles aren't consuming themselves for energy and you could still see my ribs even if I lifted all the time.