Friday, March 31, 2006

Trail Running Basics (Part 4, "Natural hazards on the Trail")

So you decided that you want to try trail running, but you don't know quite know what to do. I will tell you exactly what you will need to pursue this crazy sport in a series of blog entries.
In parts 1, 2, and 3 I've told you how to prepare for the trail. In this section, I'll describe some of Mother Nature's dangers to watch out for.

Natural Hazards on the Trail

Rattlesnakes. Rattlesnakes live all over the United States, and the Western Diamondback is found nearly everywhere in the American Southwest. Being cold-blooded, rattlesnakes are particularly active when its hot and sunny. Be especially vigilant around mid-day; they like to crawl out in the middle of the trail and absorb the sun's warmth. Make sure to scan ahead and listen for the rattle. Avoid stepping on any branches, which rattlesnakes sometimes look like. Also, avoid stepping on any mounds or holes in the ground, where a rattlesnake might be hiding. Most bites happen when you're not paying attention. Don't turn over any rocks or logs. If you do spot a snake, stop and relax. The snake is more afraid of you than you are of it. Now that you've spotted it, the odds that this encounter will end badly is nearly zero as long as you don't do anything stupid. Do not get close to it. Do not throw rocks at it or try to move it with a stick. Simply give it some time and plenty of space to slither off the trail.

If you do get bitten, call 911 from your cellphone and have an ambulance meet you at the closest road to your current location. From this point, you have about 40-50 minutes to get medical attention.

Any North American snakes other than rattlesnakes are completely harmless, so don't sweat it if you see one.

Mountain lions. Also called cougars and pumas, mountain lions are abundant in the western United States, though you'd hardly know it because these creatures are so stealthy. Attacks on humans do occur, but they are very rare. Only 6 fatalities ever have been reported in California. But because of a fairly recent fatal attack, mountain lions are on people's conscience. To avoid an attack, don't crouch down and appear to be a quadruped. This seems to be what happened to the guy that got killed. Also, be vigilant at dusk and dawn. When confronted by a lion, make lots of noise and try to appear bigger by opening your jacket. Most people are able to fend off an attack by rocks, sticks, pepper spray, or even bare hands. Mountain lions are very strong--males grow to 180 lb and can easily take down deer or even moose five times their size. But they have no endurance and not much of a will to fight, so unless they see you as an easy, painless meal they will back off.

Black bears. In the Santa Monica Mountains and Simi Hills, where I run, there are no bears. But they are almost everywhere else in California and the rest of the American West. They are less shy and more agressive than mountain lions, thus pose a bigger danger. If you run in bear country, bring pepper spray and do some research into how to fend off a bear attack. I can't help you.

Africanized honey bees. Also known as killer bees, these creatures have migrated from South America and are establishing themselves in much of the American South. They are already established in the LA area, so we might as well get used to them. The problem with these bees is that they tend to swarm when they sense that their hive may be in danger. To avoid bees, the most important thing is to avoid disturbing anything that looks like it could be a hive, especially mounds or holes in the ground.

Ticks. Ticks carry all kinds of nasty diseases, one of the scariest being Lyme disease. You can pick up a tick by brushing up against vegitation. After running, check all of your exposed skin for ticks. Wearing pants will minimize the risk.

Mosquitos. West Nile Virus has been identified in every state with the exception of Alaska and Hawaii. It's here; we have to deal with it. If you're going to run somewhere where there are a lot of mosquitos, wear deet to repell them.

Poison Oak. As I mentioned in part 3, poison oak grows almost everywhere in shady areas in California. Poison oak rashes can be excruciatingly painful. Inhaled or injested, poison oak can be extremely dangerous and may require hospitalization. Do yourself a favor, and wear pants when you run and avoid touching any leaves or branches with your bare hands, unless you have identified exactly the kind of plant that you are touching.

Wednesday, March 29, 2006

Trail Running Basics (Part 3, "Preparing for the Trail")

So you decided that you want to try trail running, but you don't know quite know what to do. I will tell you exactly what you will need to pursue this crazy sport in a series of blog entries.

In parts 1 and 2, I've talked about how get the right gear for the trail. In this section I will talk about pre-run preparation.

Preparing for the Trail

Select a course. I recommend running with a group or an experienced friend for the first few runs. They will certainly have a lot of opinions about where to go. If that's not an option, look for books describing local hiking trails. Trails that are rated "easy" or "moderate" are runnable. If you live in Southern California, pick up 50 Trail Runs in Southern California by Stan Swarts, et al. for some great ideas.

There are three basic kinds of trail course geometries: out-and-back, loop, and point-to-point. You can combine one or more loops with out-and-back or point-to-point courses for variety. An out-and-back is a little more boring than the other two since you will have to return on the same path, thus seeing the same scenery (albeit, in reverse). A point-to-point is more interesting, but requires either two cars, or a ride to the starting point or from the end point. The loop is best because you only need one car and will not need to backtrack.

Your first trail run should be an out-and-back with no loops. There are just too many places to get lost or go the wrong way when trying to make a loop, avoid loops until you're a little more familiar with the trails.

Get a good trail map. A good trail map can provide invaluable information that the little maps in you hiking book cannot. It can tell you how all the different trails fit together, where to park, which roads to take to get to the trailhead, and most importantly, how much elevation will you have to gain in what distance--this will roughly tell you how steep the trail is. For Santa Monica Mountains running, pay a visit to the Santa Monica Mountains National Recreation Area headquarters where they have a wealth of trail maps for sale (or as handouts). Once you select the trail, study the trail map and bring it with you on the trail.

Wear the right gear for the weather, and be prepared. The weather can change very quickly in the mountains, especially at higher elevations. If there is even a tiny chance of rain or strong winds, bring a jacket.

Wear pants. Unless you are sure your entire run will be on a fire road through grasslands or chaparral, always wear pants. Poison oak grows nearly everywhere in shady areas (and is not so easy to recognize), so you must protect your legs. A case of poison oak can last up to 4 weeks and is not something that you want to deal with; believe me.

Fuel up. Before hitting the trail, eat a snack, such as an energy bar, an apple, or some toast. Avoid anything with a lot of protein, fat, or fiber and don't overeat. Also, throw a bar or a couple of gel shots into your pack in case you run out of energy on the trail.

Drink some water. Make sure you start out fully hydrated before you run. I usually drink 1 liter of water (two 500ml bottles) on the drive to the trailhead. You know you are hydrated properly if you have to "use" the side of the trail about 10 minutes into your run and your urine is clear.

Fill up your hydration system. You need to drink to avoid dehydration. But you also lose electrolytes and deplete glycogen while exercising. Drinking water does not replace these. In fact, if you drink too much water while exercising you may be at risk of hyponatremia. This is a serious problem, and occurs much more frequently than you would think. So you reach for a sports drink, like Gatorade...

But wait a minute. At 212 calories for every liter, plus a huge wallop of sodium, full-strength Gatorade may not be the best choice, unless you are doing some serious distance (more than 2 or 3 hours) . In fact, you may gain weight during your run if you drink a full-strength sports drink. A better choice may be to water down the sports drink, say one part Gatorade and 4 parts water. Or you can just get Propel, which is pretty much 1 part Gatorade and 4 parts water. I love their 700 ml bottles which fit perfectly into my waist packs.

You don't need Propel; you can make your own from almost any sports drink. Just stay away from anything with high-fructose corn syrup. Fructose does not help replace your glycogen reserves. In fact, it is metabolized in the liver directly into fat, making it about as helpful as a stick of butter. (In fact, the butter probably is less stressful on the liver.)

If you are going out for a long run with a Fuel Belt, you have more options. I typically will fill up my belt with 4 bottles of plain water, 2 bottles of 50% sports drink and 50% water, and 2 bottles of full-strength sports drink.

Other things to bring on the trail.
I recommend bringing the following things on the trail:

  • ID
  • cell phone--in case you get lost
  • credit card--in case you need to call a cab to take you back to your car
  • $15 in cash: 2 fives, 5 singles--for parking or just in case (parking at the parks usually runs $3 to $7, but typically there will be street parking nearby if you want to avoid the fees)
  • Pepper spray (we'll talk about this in part 4)

One thing not to bring. Don't bring your iPod, CD player, or anything else that impairs your hearing. You will need all of your senses to avoid dangers on the trail.

Finally, make sure someone knows exactly where you're going and what time you're supposed to be back, and let's hit the trail!

Monday, March 27, 2006

Trail Running Basics (Part 2, "Trail Running Gear")

So you decided that you want to try trail running, but you don't know quite know what to do. I will tell you exactly what you will need to pursue this crazy sport in a series of blog entries.

In part 1, I showed you how to select the right shoes for the job. In this section I will talk about the other gear you may want. All of this gear is optional, but highly recommended. It sure makes trail running a lot more comfortable.

Trail Running Gear

Technical t-shirt. If you're planning on running less than 3 miles on a partly-cloudy day with little wind and temperatures around 60F, then you can get away with a cotton t-shirt. Otherwise, you'll want a technical t-shirt. A technical shirt is typically made out of a poly-blend and has some kind of moisture-wicking technology such as Coolmax or Dri-FIT. It's a lot lighter than cotton, so it keeps you much more comfortable in the heat--it doesn't get wet & heavy like cotton. When its cool, its even more important to wear a technical tee as your lowest layer, as cotton will get wet from sweat and give you hypothermia when the temperature drops or the wind kicks up. When running in temperatures below 45F, you should use a tight long-sleeve shirt. This way, your arms don't get all wet inside your jacket. You don't need to pay an arm and a leg for these t-shirts. While Under Armour has some excellent and expensive products, you can find an Athletic Works t-shirt with Coolmax at your local Wal-mart for under $7.

Nylon-shell Running Jacket and Pants. For rainy and cool-weather running, a nylon-shell jacket and pants are a must. Try to get a jacket with a little vent in the back to release heat and moisture as you run. Also, it should zip all the way up your neck. The pants should have zippers at the bottom of each leg so you can get them on and off without taking off your shoes. Both the jacket and the pants should be light enough that if it gets hot, you can take them off, tie them around your waist, and forget that they're there. Once again, these things can get pricey, but Wal-mart is there to the rescue. An Athletic Works nylon jacket and pants run around $13-15 each.

Gloves. For cold weather running, gloves are a must. Make sure to get breathable ones or they will get completely wet inside.

Hat. A hat is recommended for all occasions. For cold weather, a lightweight (wool-blend or poly-blend) beanie or ski hat works best. No cotton or anything too heavy; its easy to overheat even when the temperature is well below freezing; and once you take off your hat to cool down your wet hair will freeze--a very bad thing. For cool or rainy weather, a baseball cap works pretty well, keeping your head slightly warmer than normal and the rain out of your eyes. For hot weather, use a white mesh hat with a long brim, which provides protection from the sun and keeps persperation out of your eyes.

Shorts/underwear. I highly recommend compression running shorts. They actually help keep your quads from getting tired. Also, they are acceptable to wear in public (in case you want to take off your pants), although people will certainly get more information than you may be willing to share. Otherwise, anything will do as long as it doesn't chafe. Avoid cotton for runs longer than 45 minutes or so, as they will get wet and uncomfortable. Also avoid baggy boxers, as they are just uncomfortable.

Lightweight jogging pants. When the weather is warm and dry, you will want some lightweight jogging pants. Once again, avoid cotton. Why not just wear shorts? I'll explain in part 3.

Socks. For cold or wet conditions (including water crossings), wool-blend socks are a must. Although almost any old athletic ankle socks will do for dry conditions, don't underestimate the comfort and injury prevention that the right socks can provide. Speaking of "right socks", I highly recommend the excellent WrightSock products for blister prevention.

Hydration System. A hydration system allows you to carry fluid without having to cramp your hands by holding water bottle(s) for the duration of your run. In my experience, you will need need at least 600 ml (20 oz) of fluid per hour of running, assuming you start fully hydrated; more if its a hot day or if you weigh more than 180 lbs.

There are two types of hydration systems: bottle carriers and bladder-based systems. The bladder-based systems are typically worn on the back and can provide a very large volume of fluid. The also typically provide lots of space for food and other supplies. Because of the difficulty in cleaning the bladder (you may run into issues if the fluid is anything other than water) and the tendency to "bounce", I don't use a bladder-based system.

Bottle carriers are much more convenient but can carry less fluid. The most convenient is the single-bottle waistpack. Such a pack will have small pockets, for a cellphone, car key, ID, and a gel shot. If the bottle position is upward-facing, the pack should be worn low on the waist, with the bottle holster at the side and resting against a hip. This position virtually eliminates bounce. Most sport-drink bottles are 20 oz, which will keep you hydrated for an hour (normal conditions, fully hydrated initial state), but you can find bottles that will hold as much as 28 oz and still fit into the standard bottle carrier.

Double-bottle waistpacks have bigger pockets, allowing you to carry larger things, like snacks, cameras, and gloves. Two bottles give you twice the range, but the positioning on the waist is a little trickier and in most cases, some bounce is unavoidable.

For longer ranges, step up to the 8-bottle Fuel Belt. The Fuel Belt is by far the most comfortable hydration system with the weight of the water evenly distributed around the waist. It comes standard with a 7 oz bottles, but 10 oz bottles will also fit, giving this system a possible capacity of 80 oz or 2.4 liters. That's enough for 4 hours on the trails! The downside to the Fuel Belt is that it is rather time consuming to fill all the bottles up. Also, the tiny pocket doesn't have much space for anything more than a key and some ID. Finally, with so many different bottles, you will find yourself spending a lot of mental energy managing bottle placement by shifting bottles around. It's a bit annoying, but still better than a Camelback.

Another option is the hand-bottle carrier. I haven't tried one, but it may be a promising option for those who don't like things against their hips.

I have a single-bottle pack, a double-bottle pack, and a Fuel Belt. I use all three regularly, depending on the length of my run.

Watch. Of course you will need a stop watch to track how long you've been out and to tell what time it is. But a watch can do so much more. Especially if it has GPS. After all, there is really no accurate way to tell how far you've run without a GPS-based device. (That is, unless you are running the exact path that has been previously marked by someone with some kind of distance-measuring device). Plus, the device can tell you useful information such as altitude, calories burned, current pace, and the path back to start if you get lost. I swear by Garmin's Forerunner 201. (Prices have dropped significantly since the 205 and 305 came out; the 201 is only $99 at Buy.com, can you believe it?)

Sunglasses. The sun can do some serious damage to your eyes. So can bugs, dust, mud, and other debris. It is recommended to have glasses with some kind of sun protection. They will, incidentally, protect your eyes from debris and flying insects as well.

Sunday, March 26, 2006

Trail Running Basics (Part 1, "It's the Shoes")

So you decided that you want to try trail running, but you don't know quite know what to do. I will tell you exactly what you will need to pursue this crazy sport in a series of blog entries.

First you have to decide what kind of trails you will be running. There are two kinds of trails:
there are the ones that go from the baseball diamond to the monkey bars in your local park and there are ones that people hike on in your local mountain range. If you will be running on the former, you don't need my help. If it's the later, you'll need some gear.

It's the Shoes
The most important gear are your running shoes. One thing to remember about trail running is that you will be, umm..., running. Never buy any trail running shoes that you wouldn't be comfortable running in on pavement. In fact, you don't really need "trail" running shoes at all. All you need are a good pair of stability running shoes, especially if you won't be running in too many rocky, sandy or muddy conditions. Of course, you may want to get the trail shoes for their more aggressive tread (for traction) and their earth-tone colors (so they look better dirty).

Never buy adventure racing shoes. They are designed for races through the Costa Rican jungle, where the trails are muddy and soft. They don't have the cushioning nor stability to stand up to the trails of hard-packed earth and rock in the western United States. Rememeber, if you can't run in them on pavement, don't run in them on trails. I made that mistake once, and couldn't run for nearly half a year.

When you are shopping for shoes, stick with well-known brands that concentrate on running shoes. Do not buy a running shoe from a company that specializes in boots, sandals, or snowboards. Also, do not buy a running shoe from a company that emphasizes style over substance. Stick with big names that you trust. Running shoes have a lot of complicated technology in them that is expensive to research and develop. Small companies usually don't have the budget for it.

Some trail running shoes that I like: Asics Gel-Trabuco, Asics Gel-Eagle Trail, and Montrail Hardrock.

In my experience, its nearly impossible to find a good pair of running shoes for under $80. And since you will need at least four pairs per year (and typically more), this can be a significant expense. Budget for it. Trust me, do NOT skimp on running shoes. If you do, you will not be running for long. If you want to save some money, you can purchase last year's model (they usually run $10-20 less) if you can find them.

I recommend having two different kinds of running shoes (not the same model) to alternate. While this is not necessary, it is a little kinder to your feet since you will expose them to slightly different forces on every run.

Replace your shoes every 3 months or 300 miles, whichever comes first. If you're alternating, replace every 5 months or 300 miles.

The first time you buy running shoes, make sure you go to your local specialty running store where they carry a wide-selection of brands. (Do NOT go to Niketown or Sportmart or DSW.) The people who work there will help you pick out the right shoe for you after taking measurements and watching the mechanics of your walk. The $5 extra you will pay over Sportmart is more than worth their expert advice.

If you choose to replace your shoes from an online store, remember the following: Each shoe model will have different sizing, even within the same brand. For example, you may wear a size 10 medium for the Asics Gel-Kayanos, but you may need a size 11-wide for the Asics GT-2100s. Also, every time a model gets upgraded, the sizing may change.

Friday, March 24, 2006

Golden State Wine Tasting with Whole Foods Woodland Hills

Today, I went to a wine tasting at the Woodland Hills' Whole Foods. Cliff Riley, the wine buyer for the store, and Jim Griffin, a wine distributor, were hosting the event at the store's patio. The crowd was small, divided equally between customers and Whole Foods employees. There was toast and a cheese & olive plate to munch on. Eleven wines were being poured. Here are my notes:
  1. Scott Pail 2004 Pinot Noir "Martha Pirrie". $22. This Williamette Valley pinot was light bodied, with a bright acidity and minerality, and a peppery finish with hints of slightly under-ripe red berries. Very pleasant and seems like it would pair well a wide variety of foods. Alex's score: 8 (of 10).
  2. Fife Vineyards 2000 Merlot. $30. Bright red; not showing its age in color. Tannic merlot, a bit unbalanced in acidity and alcohol. Showing age on the palate, but grows on you. Alex's Score: 4 (of 10).
  3. Summers 2003 Reserve Merlot "Knights Valley". $22. Fine tannins and bright acidity. Understated fruit on the finish. Alex's Score: 4 (of 10).
  4. Fife Vineyards 2000 Cabernet Sauvignon. $40. Pretty bouquet of stone fruit and a touch of sweet oak on the palate. Long, satisfying finish. Alex's Score: 6 (of 10).
  5. Fife Vineyards 1999 Reserve Cabernet Sauvignon. $50. Beautiful aromas of cherry, cassis, and blackberry. Perfectly oaked with silky tannins. Very long finish. Drinking well now but should last for another six years. Alex's Score: 9 (of 10).
  6. Summers 2003 Cabernet Sauvignon "Adriana's Vineyard". $30. Warm-weather cab with great fruit and alcohol, with a streak of complexity. Alex's Score: 7 (of 10).
  7. Origin-Napa 2002 "Heritage Sites" Red Blend. $38. A right bank-style blend with 75% merlot. Hyped with only 600 cases made by two Napa dignitaries, this wine was quite a disappointment. Minty aroma, with menthol and bell pepper dominating the palate. Alex's Score: 2 (of 10).
  8. Arns 2001 Cabernet Sauvignon. $70. The only long ager in the group, this wine is a baby at 5. A well-oaked, technical masterpiece with excellent structure, perfect balance, and a long earthy & fruity finish. Alex's Score: 8.5 (of 10).
  9. Summers 2002 Zinfandel "Adriana's Vineyard". $22. Elegant Zin; well-balanced and fruity but not jammy. Subtly oaked with a curious complexity. Alex's Score: 8 (of 10).
  10. Fife Vineyards 2000 Petite Syrah "Redhead Vineyard". $30. With a very pretty bouquet of blueberries and earth, this Pet is well-aged and thus restrained on the palate, with low tannins. The finish lasts forever. Alex's Score: 8 (of 10).
  11. Elimilio Lustau Sherry "Rare Cream Superior". $13 (375 ml). With a sickeningly-sweet aroma of crème brûlée fresh from the torch, I was prepared to hate this wine, but it was surprisingly balanced on the palate, with bright acidity and simply delicious flavor. A sure hit with almost any kind of food, this Sherry can also be enjoyed on its own as well. Alex's Score: 7 (of 10).

All in all, I had a great time. Kudos to Dimple for buying me the ticket and making me go!

Thursday, March 23, 2006

Inflammation and injuries

On a beautiful Tuesday afternoon in late July 2005, I went for a run of 5 miles on a very steep trail at Ahmanson Ranch. This was supposed to be a recovery run from the previous Sunday's 10 miler at Point Mugu that I did with the Trail Runners Club. For the past two weeks, I was wearing flimsy adventure racing shoes that did not have proper cushioning or support (but sure looked cool) for trails. At the tail-end of the run, I took the downhill particularly hard. As soon as I got to the car, I knew something was wrong. My feet hurt like hell. It was a different kind of hurt than normal. I ignored the pain as usual, assuming that it would feel better tomorrow, or at the worst, in a couple of days. Of course, it didn't. I had plantar fasciitis.

Five and a half months later (and after a month of intense stretching and icing therapy), I was finally able to complete a flat one-mile run without too much pain.

The root cause of my plantar fasciitis, as well as most over-use injuries, is inflammation.

This article talks about a supplement to help with inflammation. This "HIMF" thing sounds promising. I may just give it a try. Will it'll help with the knee problems that I'm currently having? Time will tell.

Wednesday, March 22, 2006

Ahmanson Ranch after the fire

On September 28th a small brushfire started in Chatsworth. Blown southwest and enflamed by the Santa Ana winds, the Topanga Fire (as it came to be known) burned through a large chunk of the Simi Hills and affected much of the Conejo Valley (where I work) and the western-most San Fernando Valley (where I live). For several days, we stayed inside with the windows closed and the air conditioner on full blast, trying to avoid the smoke (with little success). Outside, ash was raining down on our neighborhood like snow. Luckily, the winds died down and the fire was contained. There was remarkably little property damage and no lives were lost. Nevertheless, the area stunk like smoke for weeks (if not months) afterwards.

Much of the fire fighting effort was centered around Ahmanson Ranch, an open space preserve where I spent a lot of time trail running in the spring and summer of 2005 (before my injury). The fires there were threatening communities in West Hills, Hidden Hills, and Calabasas.

In December, I went back to Ahmanson Ranch. Nearly three months after the fire, it still smelled like smoke. But it was starting to recover. I felt like I was witnessing a moment of birth. It was a magic, beautiful landscape that described the cycle of life in stunning detail.

I went back to running in Ahmanson Ranch in February. By then, the landscape had changed. There are still many reminders of the fire, but the magical moment has passed.

Here are some photographs that I took.

At the LA Auto Show

A couple of months ago I dragged Dimple and Joshua to the LA Auto Show. While being in a crowded space with a rowdy toddler was rather stressful for Dimple and I, we still managed to have fun. But Joshua had the most fun of all. Approximately 80% of the toys that Joshua actually plays with are some kind of toy cars or trucks. For him, the Auto Show was like a giant toy box.

The $100,000 Gucci-branded Chrysler 300 Royale was a big hit with Dimple:


She also liked Chrysler Crossfire-like concept sports car:


Joshua enjoyed running around all over the place, yelling "Beep, beep!" and "Vroom, vroom!":


He was intrigued by VW's V6 and had to check out the inside of the new Jetta:


Joshua wanted a snack, so Mommy bought an ice cream to share with Daddy:


Energized, it was time to play with the controls of a Suburu Impressa. Joshua and I both agreed that the interior left a lot to be desired:


While I went to check out the new Infinitis, Joshua found a make-shift slide at the Honda exhibit:


Joshua thought the Mercedes-Benz CLK convertible fascinating:

The hidden cost of software features

The goal of every software development project is to deliver features for an application.

At the beginning of every project, key stake-holders get together and decide which features should be built, and debate on what are the relative priorities of each feature. Features may be cut due to low priority or high cost of development.

During this process, issues that add to the "hidden" costs of features are often overlooked. Of course, these issues must be taken into consideration to assess the true cost of developing a feature:

1. Does the target user of the application care about this feature?

They may say they want the feature, but want is quite different from will use. In my experience, users always want as many features as possible but actually wind up using the most minimalist feature set that still allows them to accomplish their task.

2. Will this feature negatively affect the user experience?

Adding features to an application is not for free. Every extra UI widget adds clutter and reduces usability. (Skeptical? Which interface is more pleasant to use, Yahoo or Google?) Every option forces a decision that users do not want to make or even expend any intellectual energy on.

Often trade-offs in user experience have to be made to accommodate this feature. For example, the user may have really wanted a spell checker, but not enough to have to wait an extra 90 seconds on every "Save".

It's amazing how often new features added to an application break the clean user experience or quick response time that attracted users to this application in the first place.

3. How long will the feature need to be QA'd and UAT'd?

Just because something takes 1 hour to implement, it doesn't mean that it will take 1 hour to test.

4. Does this feature compromise our architecture?

Every new line of code adds potential complexity to your code base. It creates a new point of failure. There is no way to prevent this, but there are ways to mitigate it. Developers need to be cautious about adding unnecessary (or harmful) layers, classes, properties, methods, parameters, etc. They need to think about how this new thing they're adding will affect the stability of the architecture. For example, it would be really easy to expose the database ID of this object as a public property to solve the problem of finding the object again, but suppose you switched databases, or decided to go with XML as your backend, and now all of those modules that depend on that ID will be broken.

There will always be a way to implement the feature in an architecturally-sound way, but it the cost may be higher than originally thought.



Tuesday, March 21, 2006

Does Joshua have a career as a high-powered executive?


He sure knows how to handle that cell phone and he looks like he means business.

Welcome to my blog

I published my first personal website in early 1994, and the very first item I put on there was an under-construction icon. Ever since then, for almost 12 years, the spirit of that icon has stayed with my personal website. It has taken me this long to realize that I will never have the time nor the inclination to create the kind of content that I would like. Even keeping my son's baby pictures current is a task that is far beyond the kind of commitment that I can realistically make.

Blogging is a much better solution than maintaining a full-blown website. I can post small commentaries on topics that interest me, such as software, trail running, and wine without having to create an entire page devoted to each topic.