Occasionally I get asked what motivates me to run on a regular basis. For me, running is fun. I wouldn’t do it if it wasn’t. During the run, I take pleasure in partaking in an activity that I believe Homo sapien sapien was designed to do, and after the run my body feels better.
If that’s not enough, try this: In his autobiography Mad, Bad & Dangerous to Know, Sir Ranulph Fiennes said that, now in his late sixties, the only way he can manage to keep up a decent level of fitness is to run at least 2 hours every other day. I’ll not be physically bested by an old man, even one such as Fiennes!
Sealed in their metallic shells like molluscs on wheels, how can I pry the people free? The auto as tin can, the park ranger as opener. Look here, I want to say, for godsake folks get out of them there machines, take off those fucking sunglasses and unpeel both eyeballs, look around; throw away those god-damned idiotic cameras! For chrissake folks what is this life if full of care we have no time to stand and stare? eh? Take off your shoes for a while, unzip your fly, piss hearty, dig your toes in the hot sand, feel that raw and rugged earth, split a couple of big toenails, draw blood! Why not? Jesus Christ, lady, roll that window down! You can't see the desert if you can't smell it. Dusty? Of course it's dusty -- this is Utah! But it's good dust, good red Utahn dust, rich in iron, rich in irony. Turn that motor off. Get out of that piece of iron and stretch your varicose veins, take off your brassiere and get some hot sun on your old wrinkled dugs! You sir, squinting at the map with your radiator boiling over and your fuel pump vapor-locked, crawl out of that shiny hunk of GM junk and take a walk -- yes, leave the old lady and those squawling brats behind for a while, turn your back on them and take a long quiet walk straight into the canyons, get lost for a while, come back when you damn well fell like it, it'll do you and her and them a world of good. Give the kids a break too, let them out of the car, let them go scrambling over the rocks hunting for rattlesnakes and scorpions and anthills -- yes sir, let them out, turn them loose; how dare you imprison little children in your goddamned upholstered horseless hearse? Yes sir, yes madam, I entreat you, get out of those motorized wheelchairs , get off your foam rubber backsides, stand up straight like men! like women! like human beings! and walk -- walk -- WALK upon our sweet and blessed land!
-Edward Abbey, Desert Solitaire
I was up around Lake Twenty Two yesterday, further exploring the area and testing small changes to my gear load out. I was surprised at the amount of snow I encountered. There was a good foot of it around the lake, whereas at the end of January there was only a dusting. Winter and Spring seem to have gotten themselves confused.
It’s been nearly two years since I last redesigned this site. Don’t let me go that long again! The web is supposed to be a dynamic place, you know. Anyway, here’s the new look.
It isn’t drastically different from the old one. I’m still keeping it clean and simple, and the base colors are the same.
You might notice the rounded corners on some things. Yeah, that’s right. Web 2.0, here I come! I think rounded corners are only acceptable if accomplished with simple CSS. CSS3 is slated to include the border-radius property to achieve rounded corners. The specifications are not yet finalized, but Mozilla browsers have implemented the property with -moz-border-radius and WebKit browsers with -webkit-border-radius. Those are the properties that I’m using. That means you’ll get rounded corners in browsers like Firefox and Safari. Opera seems to work too. Internet Explorer, not so much. (Come on, IE has a hard enough time complying with current standards. You can’t expect it to look to the future!)
If you notice any bugs or would like to suggest any changes, let me know. After all, the site is really for you, dear user.
(I did briefly look at everything on a Windows box running IE8. It seemed to work – other than the rounded corners, of course – but if you notice any bugs in that particular browser, you know the drill.)
Two of the things that really spurred this design are Readability and Clippable. For about a month now, I’ve been using these bookmarklets while reading longs articles online. They help a lot. But it’s really a problem with the design of some sites that I feel the need to use them. I decided that I wanted to redesign my site with typography in mind.
I’m also now integrating Twitter posts into the blog. We’ll see how that goes. They’re styled differently, so there is a visual distinction between a tweet and a normal post. The idea is that I’m now just using twitter as a back-end to create short posts. If I want to, I can switch to some other microblogging service and you, the user, need never know the difference. (I could even just use Wordpress to create short posts! But that might get me kicked off the interwebs…)
Tweets integrated into the blog means tweets in the RSS feed, as well. That makes my RSS mash-up a bit irrelevant. If you currently subscribe to that, I’d recommend changing your subscription back to the normal feed. For those who don’t want to change, I’ve removed the Twitter feed from the mash-up’s input. That way you won’t have to read each of my tweets twice. The mash-up feed will now only include the blog and Flickr stream.
Blueprint
This design is built upon the Blueprint CSS framework. I’ve used it a handful of times before, but never properly. My method was always to link to the three Blueprint CSS files (screen.css, print.css, and ie.css) in the header and then toss in a link to my own stylesheet underneath them. I never used the compressor.
The idea behind the compressor is pretty simple. It allows you to maintain one central instance of Blueprint and use that to generate the CSS needed for each individual project.
<ul><li>Keep a core Blueprint folder checked out with <ahref="http://git-scm.com/">Git</a> on your computer</li><li>Create a settings.yml file within the Blueprint folder with all the specifics of each project using Blueprint</li><li>Use the command line to generate <spanclass="caps">CSS</span> for a project on command
<ul><li>Incorporating any site-specific attributes
<ul><li>Namespace on all Blueprint classes</li><li>Custom grid template rather than the standard 24 columns / 30px column width / 10px gutter width</li></ul></li><li>Compressing any custom <spanclass="caps">CSS</span> and appending to the end of the Blueprint stylesheets</li><li>Appending custom semantic selectors to the end of the Blueprint stylesheets</li></ul></li></ul>
When I first head about this, I though that the compression bit was all well and good, but I’ve never been really adamant about optimizing CSS for speed in the first place. I’m more concerned about compliance with standards and readability. Maintaining a central Blueprint instance didn’t appeal to me much, either. What really stood out is the ability to have custom semantic selectors.
CSS frameworks are neat. I’ve used a handful. Like any other tool, they’re not always appropriate. When they are, they have certain advantages and disadvantages. One of the main things that I dislike about them is that they encourage you to clutter your code with framework-specific junk. If you’re using 960.gs you’re going to have elements with classes like “container_x”, “grid_x”, “omega”, and “suffix_x” all over the place. With Grids you’ll have “yui-g”, “yui-b”, “yui-main”, and the like. Readability of code is diminished and you’ll probably end up suffering from a case of div-itis. Not to mention, you can forget about a strict separation of markup and styling. Sure, you could copy the style definitions for the specific framework classes into the classes or IDs of your own elements, but how many folks actually take the time to do all that copying and pasting? I sure don’t! The appeal in a CSS framework is to save time, not make the process of building a site longer. Plus, there’s an appeal in having the framework-related styling separate from the normal site styling. Such a separation makes the framework easy to update.
This is where Blueprint’s semantic classes comes in. It allows you to tell Blueprint to take one of your classes (or IDs) and apply to it the properties of one of Blueprint’s classes. A-mazing.
As an example, the header of this page might look something like this if built on Blueprint without the compressor:
Clean as a whistle! No useless divs, all elements semantically named, and not dependent on any framework.
As great as the compressor is, I do have a couple problems with it. When using the compressor, Blueprint intends that you only have 3 final (compressed) stylesheets: screen.css, print.css, and ie.css. Wordpress, of course, requires a style.css file to define the template. That’s no problem. I just a create a style.css file that has the theme information in it and then toss in a @import url(‘blueprint/screen.css’). Then in the Wordpress header I can put a link to style.css, print.css, and ie.css. Everybody’s happy.
Styling a website basically boils down to making a small change to the stylesheet and refreshing the page to see how that looks. Running the compressor after each change to combine the custom stylesheet with the screen.css file is not productive. So for the development process I tossed a @import url(‘blueprint/custom.css’) into the main style.css file. That works fine.
Then I finish building the theme. I’m ready to compress the stylesheets, so I remove the call to the custom stylesheet in style.css. I tell the compressor where the custom stylesheet is and have it combine it with the screen.css file. I run the compressor, reload the site, and everything explodes.
Just when I thought I was done!
The problem is that in the stylesheet the compressor generates, it puts my custom styles above the semantic classes. Throughout the development process, I was calling the screen.css file (which includes the semantic classes) before the custom stylesheet. As you no doubt know, stylesheets cascade. You can’t just switch up the order of elements without breaking stuff.
Oh well, I thought. At this point I was tired working on the site and didn’t care enough to fight it. I just put the line to call the custom sheet back in style.css after Blueprint’s screen.css file. I still feel like the whole semantic classes bit is enough of a reason to use the compressor, even if I’m not actually compressing my main stylesheet!
In the past, I used Camelbak bladders as my primary water reservoir. I’ve had three of their military hydration systems and never experienced a leak – except once when I neglected to fully close the bladder’s lid. In snowy, alpine conditions I would chuckle at others whose hydration hoses were frozen shut, while I confidently sucked on my insulated Camelbak hose. The Camelbak mouthpiece always insured a high flow-rate, unlike some other brands, and the hose could be shut off at either end, providing further protection against the accidental leaks that have been known to plague other bladders.
But the Camelbak’s durability comes at a price. My 100oz Omega Reservoir (including bite valve and insulated tube) weigh in at 10oz. Not exactly light. So last year, I decided to give Platypus bladders a shot. I had been critical of their toughness in the past, but their 2 liter bottle weighed in at only 1.4oz. With optional drink tube kit and bite valve cover, the full system weighed 3.6oz. It had been referred to as the “gold standard” in ultralight bottles. Too enticing not to pick up.
Of course, the low weight of the Platypus system also comes at a price. The small opening makes the bladder less convenient to fill. The tube is uninsulated, and so inappropriate for much cold weather use. The bite valve has a low flow rate and is prone to leaking. The bite valve cover is cumbersome and difficult to close. And the bladder itself is made of a much thinner and less durable plastic than the Camelbaks. Still, I have been very happy overall with the 2L Platypus bottle. I have not touched the Camelbak once since making the conversion.
But now my Platypus has begun to leak. I’ve patched it with Gorilla Tape, which seems to be an effective fix, but it is only temporary. I need to replace the bottle. Nowadays, all the rage seems to be for the new bottles with their ugly colors. The largest of these is 1 liter, and so not an option for me.
Platypus also now offers two newer hydration systems. The first is the Hoser, which is similar to the old bottle, but with a grab loop at one end and an angled port at the other. The manufacturer’s weight for this system is 3.6oz, which is the same weight that I have measured for my old bottle, hose, and valve. The trouble with the Hoser is that the bottom does away with the traditional expanding bottom of the old bottles in favor of a grab loop. Because of the small opening of the bladders, the best way that I have found to fill it is to scoop up water with something else and pour it into the standing bladder (a method made popular by Jason Klass). For one person to achieve this, the bladder has to stand on its own. The Hoser bladder will not, so it isn’t an option for me.
The other new offering from Platypus is the Big Zip SL. The zipper closer on this addresses the difficulty of filling. The manufacturer’s listed weight is listed at 5.5oz (though I’ve heard reports that it is actually heavier): still a good deal lighter than the Camelbak, but significantly heavier than the old bottle system.
I could go back to the old Camelbak, but the weight deters me. It is also difficult to pour precise amounts of water out of the Camelbak bladder for cooking, which is a disadvantage now that I’m used to the Platypus bottles.
The other option is a bladder from Source. I first heard of these with MilitaryMoron’s review. They have many features that are attractive to me, but I haven’t seen anybody post an accurate weight. Source themselves list their 2L bladder at 0.53lbs (8.48 oz), but they have the same weight listed for the 1.5L and 3L bladders. It seems highly improbable to me that three different sized objects weigh exactly the same. More likely, the manufacturer’s listed weights are inaccurate. I am assuming that the Source bladders will be heavier than the comparable Platypus Big Zip SL and that they have the potential to be slightly lighter than a Camelbak, but that is only a guess. I would rather not purchase a Source bladder without knowing an accurate weight.
For now, I think I will buy another 2L Platypus bottle to replace my leaky one. Despite the durability issues, they seem to be the best mix of price, performance, and weight. They must be thought of as disposable, but that is true of all plastic water carriers. I’m not sure why they have lately become more difficult to acquire from large retailers.
Does anybody know of any other options that I have overlooked?
ITS Tactical is a site that, in their words, is dedicated to living better on the tactical side of life. The site only launched in April of 2009, but with its tutorials, gear reviews, and other articles, has already established itself as mainstay in the community. I first discovered ITS last summer, and it immediately became one of my daily reads.
Last week, Bryan, the editor-in-chief, contacted me and said that he was interested in featuring my work with the DIY Tyvek Stuff Sacks on ITS. I had been meaning to rewrite that article, anyways, in order to demonstrate my new method for constructing the sacks. So I jumped at the opportunity to be a guest writer for ITS. You can see my article on ITS right here, and all the photos are of course available on Flickr.
I decided that I wanted to do something useful with my links page, so I’ve updated it to list those blogs that I subscribe to with my feed reader. Currently, there are 59 links. I’ll try to keep the list updated as I stop reading old blogs or start to read new ones.
Remember Mailbox Peak? The mountain that was supposed to provide one of the most difficult, thigh-burning day hikes in the region? When I climbed it last October my reaction was a cocky “Psch. That ain’t no challenge! Maybe will a full pack it’d cause some pain.” Yesterday, I climbed it again. This time with a 60lb rucksack on my back.
Reaching the summit took three exhausting, slow hours. I allowed myself only one 10 minute break each hour. For the last quarter of the hike I was just stumbling along, slowly plodding my way up higher and higher (thinking “Whose bright idea was this?”). The trail near the top was too covered with snow and ice to make it smart to attempt without some sort of traction device, so I opted for the neighboring boulder field. Scrambling up that required more leg power, balance, and mental facilities than I had left at the time, but I managed to make it.
Upon reaching the summit, I immediately dropped my pack and sat down. I could only relax for a minute before realizing that I was freezing. And so I had to exert myself further by grabbing more layers from my pack and tossing them on.
I realized that I was dizzy, shaking, and – despite having been constantly sucking on my hydration hose on the way up – not sweating as much as I felt that I should have been, so I took a packet of Emergen-C from my first aid kit, dumped it into one of the 1 liter water bottles I had been using for weights, and forced myself to drink it all down before starting my descent.
I felt better after that and, munching on some granola, wandered around the summit, enjoying the view. It had been a spring-like day, with only a few clouds and temperatures around 50F at the bottom. Gazing at the other peaks with their light dustings of snow, I decided that the hike had been worth it.
There was only one mailbox up there this time. The black one must have blown away.
I decided to head down. The boulder field was tricky going, but, afterward, it was just a slow and steady plodding down the mountain. Near the bottom I had to poo, but, upon assuming the position, discovered that I didn’t have the length strength left to squat.
Finally, I made it back to the trail head, around two and a half hours after leaving the top. That night I had energy only to shower and eat a double serving of oatmeal before crashing. Today, I am stiff, but not as sore as I thought I would be.
