Thursday, October 14, 2010

Output > Input

While feng shui'ing the documentation of our flagship product--per Client Services's suggestion--it occurred to me that I'd made the same error in writing as I often do while writing user interface (UI) code.

When coding, I have the tendency to obsess over validating input to avoid data being corrupted and leaving the question of UI to Those Who Know Best. In writing, I spent so much time attempting to make sure the user entering/manipulating data didn't hose it up, that getting meaningful data back out was shoved to the proverbial back burner and more or less left to scorch.

The truly pathetic part is, I started that documentation something like eight years ago, and only realized the deficiency now.

Moral of the story: Don't be me.