Friday, March 30, 2012

Short Table

This sounds like a post about carpentry. I wasn't going to run today, but I'm not sure what I'm doing tomorrow (i.e. if I'm going to be able to run), so I did a short easy jaunt to the top of North Table and tried to find the trail around the southeast side.

A) I think the North Table Loop "under construction" on the map does not exist yet (unlike Cottonwood Canyon, which seems complete). B) There's an existing social trail from the Fairmount trailhead on Easley Road, so I took that to Mesa Top, then up past the waterfall to the summit plain. I think the dashed line on the far right of the map near #2 is that social trail. As far as I can tell, the connecting section on the lower right has not been built yet, and there is not even a social trail there.

The easy way up/down the mountain is shown below, and involves four legs. There are lots of stables in the neighborhoods below the mountain. Yesterday I ran past riders practicing, and horses being fed. Horses are omnipresent out here, even in suburbia.

The waterfall is currently a mere trickle:

To run on top of this mountain, away from all cares and with an expansive and crazily colorful sky above, is a good way to spend the late afternoon after work.

On top of that, I heard that my uber-boss told our direct bosses that even though we have an important goal due next week, he didn't want staff burning the midnight oil, so we all went home at a normal hour and will have normal weekends. The workload was tailored to be realistic and to emphasize quality over hurried quantity. This is not the last software release in the world, after all.

I'm grateful for that simple command. Simple things matter.

Because now I can do this run, and take these pictures.

Distance was 6.49 miles, time 1:24, elevation gain/loss 875 feet, avg. pace 13:05, and best pace 7:10.


  1. GZ - No doubt. Smart move IMO, which can turn a release from something to dread into a positive occasion.

  2. Great pics, looking forward to another one with a heavier waterfall flow.
    And I really hope that looking at a waterfall didn't make you think of a software development model! Seriously, hope you don't get too burned out, and glad your boss backed things off. Sadly, schedule problems always hit engineers the hardest -- like the end of a whip or a rollercoaster cresting a hill -- despite significant contribution from management on schedule and resource decisions. (Preaching to the choir hear, certainly...)

  3. Mike - Thanks. May have to wait until the thunderstorms start for that waterfall. Pretty dry up there.

    The boss is a longtime advocate of agile development, and seems to be very willing to prioritize so as to not overload us. The long-time employees who used to do waterfall, and who have spent years regarding each release as if it were the last plane leaving wartime Hanoi (and therefore an occasion for cramming too much stuff in), are coming around.