Disambiguate LINQ and Lync with Skype
If you’ve been following along this little blog experiment, you probably know that I relish in all things LINQ. More and more often, I’m finding that when I tell people I love LINQ and wrote a book on it, they start to ask me if I can help them migrate their communication server to Lync. I’m dumbfounded when the confusion occurs in people who should know better (.Net development managers).
It’s not completely their fault. The fault lies in the Microsoft marketing and branding teams that aren’t aware of the breadth of their product offerings in other areas. As a result, we have a situation where two unrelated products have the same name (or are pronounced the same in English). Like many of you out there, I’m often saddened when I see Microsoft marketing take a really cool name (Avalon, Indigo, Astoria) and distort it into something dry, boring, and utterly unsexy. Don’t even get me started on how they changed my “Become an Rx Pusher for WP7” title from Mix into “Rx: A Library for Managing Asynchronous Data and Events in your Windows Phone 7 Application”. Now, they’ve neutered the kinq of LINQ by creating another product with the same name.
If' they’re smart, Microsoft should leverage their recent 8.5 billion purchase and resolve this travesty by rebranding Lync as the new Microsoft Skype Unified Communication Client (Mi-Succ).
Do you have a better option, leave a comment and let me know what you thync. Or if you prefer, skype me with Mi-Succ (Skype).