Ok, I don't mean why shouldn't I work, I mean why don't I post about work.  I've gotten a couple of emails about this and author J.C. Hutchins just pointed out an article indicating that your blog is your resume.  So, here's the flipside of that...

In short, it would be somewhat unethical for me to post details about my specific job and the company I'm working for.  In cases like this, posting any real pertinent info about my job would probably be the quickest way to make sure that I no longer have one.  When I run into odd situations that are out of the norm and I think it would be beneficial for others to be able to refer to them, I'll post them up with as little detail as possible (but still enough to point peeps to the right resources).  Most of my Exchange and Powershell posts fall in that category.  Anything more specific than that would be hazardous to my career.  Especially when I know people at the office occasionally read my blog (I'm not the only high-tech-redneck here).

I can give you a bit of background on my job though...  I'm basically a "messaging architect".  I design, implement, support and troubleshoot all things dealing with electronic messaging at the company I'm at.  This includes Exchange, Blackberry, Windows Mobile, electronic faxing, web-mail and application integration.  Of course, you can't do that kind of stuff without also being somewhat responsible for server setup, infrastructure design and policies, clustering, Active Directory management, DNS, etc.  In short, I pretty much have a ton of access to a ton of stuff.

Anything I post about my work would be useless without technical details.  Unfortunately, posting technical details about how we're set up and how we do things would open the door to nefarious individuals.

So, with that in mind, don't expect any real solid information about my work life here.  I may occasionally post up some technical tidbit, but otherwise it's all going to be non-work-related spew.