About

Why This Blog

Because it should be documented. I spend a large amount of my time at work searching the internet for different error and symptoms. Most of the time the first link on Google tells me what I need to know. However, there are some times when I can search for hours and not find a concrete answer. At this point I generally resort to poking and prodding at the software until I figure out how it works, or rather, how it doesn't work. 

And then I go on my way - occasionally I'll make notes on our private documentation server, but for the most part what I've figured out doesn't ever get written down. It occurs to me that, given the amount of time I spend searching the web for obscure problems, to find a solution that no one else has written down, then not write it down myself is kind of a dick thing to do.

So here I am attempting to put out on the internet, in some form that should be available through search engines, a list of problems I've solved that did not have solutions readily available. 

One of my favorite things about my job is the number of different technologies I get to work with. However, since I'm generally fixing problems with different software, on different platforms from day-to-day, this will probably give this blog a very disjointed and schizophrenic feel. Of course, if I do it right, no one will probably ever notice because they'll find the page they're looking for through google and not read anything else; not even sure why I'm bothering to write this, acutally.