My direct team at Microsoft, which owns content for Visual Studio (pretty much everything you see under has a new opening for a Content Developer! All the details are on the Microsoft Careers site for job ID 286233. This posting is for a junior position, as the experience bar is set at only 2 years of software-related work, even if it's not directly in content.

What is a Content Developer? Well, we are responsible for the Visual Studio documentation, but content also includes working on videos, sample code, and anything else that helps developers understand how to be productive with Visual Studio and other related tools (I handle the NuGet docs too, for example).

Perhaps this doesn't sound as glamorous as writing code, but consider this: the primary factor today in the adoption of a technology is content, not features. Knowing this, us content developers strive to make that content experience the best it can be because it has so much impact on the success of the products. As Miguel de lcaza tweeted, "When I ask myself "what would have the most impact today?" I sit down and write documentation."

So come join us and have that impact yourself. You can apply directly, of course, but also feel free to contact me directly for more, including @kraigbro on Twitter.

It's been some years since I got an email related to COM and OLE, and in this case it was Lun Ui of who identified a bug in the iclass.cpp files of the Cosmo Server implementation that caused a failure. Specifically:


STDMETHODIMP_(ULONG) CFigureClassFactory::Release(void)


    if (0 ==–m_cRef)  // BUG: should be !=

        return m_cRef;


    delete this;

    return 0;



Thanks, Lun!


Among other extracurricular projects, I'm in the final stages of a new non-tech book called Solving Stress: The Power to Remain Calm and Cool amid Chaos, to be published later this year from Crystal Clarity, Publishers (cover design below). Unlike many books on stress reduction, this one goes to the heart of why were experience stress in the first place and looks at solutions from that standpoint, providing then some very direct and effective exercises—one’s I’ve personally used for many years.

I'm now specifically looking for reviewers who would be willing to write a supportive testimonial. For obvious reasons, I'm especially interested in those of you who have meaningful credentials that look good on the tag line of the testimonial. For example, higher degrees, books that you've authored, some standing in your industry or profession, etc.

If this is something you'd be willing to do, let me know via the Contact page and I'll get a PDF to you. I would need the testimonial by end of June, but don't worry, the book is only 138 pages which includes filler pages and a number of illustrations, so it's a reasonably short read!