Having been on the Unified Communications team for over two years now, I thought it might be time for me to join the blogging community. When I first arrived on the team, many of my peers already were publishing blogs and not being as comfortable with the product, I didn’t feel qualified to post one of my own. However, as time has progressed, I think I am ready to take the plunge. I rely very heavily on my teammates for their knowledge and experience on a daily basis and cannot thank them all enough for this. That being said, I often find myself searching for information on a topic and not finding anything on it. So, I thought that must be my opportunity to create a blog! So here we go.
Before I get into my technical postings, I would like to a moment to again thank my team both locally and across site for all the support and knowledge they have shared with me. Without them I would not be able to do my job, period. The Unified Communications team is still small, compared to Exchange or some other products. That doesn’t change the quality of the work one bit, I assure you. The team consists of both new as well as senior engineers, developers and managers that make working in this environment a true pleasure. Thanks folks, thanks for everything.
Also, since some of those teammates do publish blogs of their own, I would like to specifically mention them here. This list is by no means a complete listing of all blogs related to UC, but the ones that I know personally and have relied on daily for the past 2 years.
In addition, there are literally hundreds of blogs related to UC, created by employees, solution providers and customers too. All valuable in their own way, here is a link to a recent list of all UC blogs; http://communicationsserverteam.com/archive/2009/08/11/550.aspx
Finally, there are a couple of UC related Twitter feeds you might want to follow as well;
Now after composing this post and seeing all the great knowledge already published out there, I am back to wondering what could I possible add to this? Well, we will just have to see. :)
Mark “/\/\arkBarr” Barringer