About Kent Cowgill
Articles filed under...
abs ab_ripper andylester arms back baggyshorts bestpractices biceps bike birthday blog bugs bus calculator cardio catalyst cgi chart chest chinups code cpan datamodel dbi doctor documentation exercise exhaustion fitness flattire flat_tire google gps heart_rate helmet history home houston html humor journal kate kenpo kenpo_x kettlebell knees lazy legs lisa lisanne maps math matthew michaelmckenna mom montreal motivation movie mysql oops orm P90X pain park patellar_tendonitis patrick pdf perl phb photos physical_therapy plyometrics poor_gait presentation procrastination progress pullups pushups pyramid rabbits racecondition rant refactor rest ribs ride route running shoulders situps slides sore spike sql statistics syntax test testing textile timex training triceps ups versioncontrol video vim vimrc walk warren work workouts yapc yapcna2007 yoga youtube

A R C H I V E S

(3)
(1)
(3)
(2)
(7)
(15)
(16)
(25)
(3)
(4)
(2)
(4)
(11)
(1)
(1)
(3)
(2)
(2)
(10)
(5)
(2)
(3)
(4)
(9)
(21)
(3)
(3)
(1)
(6)
(4)
(1)
(4)
(3)
(2)
(1)


    Is Kent Cowgill Online?
    View Kent Cowgill's profile on LinkedIn
    Add to Technorati Favorites

    Recent Entries...

    Re: Re: Yoga kicks my butt

    Chris @ 46: Tatyana @ 21 – at best its a stop gap measure...

    Re: Vibram FiveFingers FTW

    Hats off to whoever wrote this up and potesd it....

    Re: A little more detail on using a new model

    百度 [url=http://www.sina.com]sina[/url] ...

    Re: Catching up through week 7

    testing video ...

    Re: Porting a non-Moose object to Moose

    Wow, look what I found, greedy genius ...

    Re: Porting a non-Moose object to Moose

    Kevin, You're right, that does seem a little confusing. ...

    Re: Porting a non-Moose object to Moose

    Wait. I'm confused. Moose isn't the tool to reach for. So...

    Re: Porting a non-Moose object to Moose

    You should switch to MooseX::Types to declare your Typed and...

    Porting a non-Moose object to Moose

    I'm currently working with a lot of legacy code in an envi...

    Testing strategy for mocking code

    I keep finding myself using the following idiom for writing ...

    weblog | `web·lôg -läg |
    noun
    Another term for BLOG
    ORIGIN 1990s: from web in the sense [World Wide Web] and log in the sense [regular record of incidents.]
    blog | bläg |
    noun
    A web site on which an individual or group of users produces an ongoing narrative.
    ORIGIN a shortening of WEBLOG.

    Finishing up week 1 of the push ups and chin ups

    Kent Cowgill

    July 18:
    Whoops. I meant to do week 1 day 3 today. Good thing I didn't, because...

    July 19:
    Seems like I needed to rest up for the big effort.

    Push ups: 15 then 13 then 10 then 10 then maxed out at 16. And a half, but I'm not counting halves. Resting about 2 minutes between sets, for a total of 64 push ups within about 10 minutes. These felt pretty good, except for the last few of the last few sets. It seems like I'm well on my way to being able to do 100 in about 6 weeks, at least according to hundredpushups.com. I just hope I can keep this up. For the push ups, anyhow. Because next up were...

    Chin ups: 5 then 4 then 3 then 3 then maxed out at 3. At least 3 short of the goal of the program. I rested about 2 minutes between sets for a total of 18 within about 9 minutes or so. So 5 more than on Wednesday - so at least that's something. But because of my failure to hit the mark, I think I'll repeat this whole week. Which means I'll have a bit easier of a time hitting my number on Monday. I briefly considered just repeating today's program until I got it, but I struggled every day of the week 1 program applying it to chin ups. I'm thinking that for push ups, the schedule is realistic - since push ups seem like they're easier overall than chin ups. But chin ups are a little tougher, so it might take a little longer then the 6 week goal. Like maybe twice as long. But that's OK - 100 consecutive chin ups would be a very impressive feat.

    For the geeky update, I've created the graphing code which currently just tracks 3 weights: total body weight, lean body weight, and fat weight. I decided to let the user decide how big a graph they wanted see, which could be problematic. The graph is weight by day, so if a day is missing (i.e. the user only weighs/measures himself once a week) then when asked to show a graph for 10 days, there may be only one data point - and there wouldn't be any outliers to graph against. So I decided to, given a particular cutoff, backtrack until the next most recent data point was located.

    Related Photos: None

    Main Page | Login

    Do you want to buy me ? Find more gift ideas at my wishlist