My company is an IT consulting shop that provides Infrastructure and development solutions. Our solutions, and our entire business model, are based on the product stack of one particular software ISV; we'll call this ISV "Acme". Acme's existence and products are essential to our business, and we are in the elite ranks of their channel partner status. We are huge advocates of them, and they of us.
I recently stumbled across the personal, public, blog of one of my developers. I've copied some snippets below (my edits are in brackets):
"C'mon [Acme]- We know it's the year 2007 because we're smart. You know it's the year 2007 because you released this next version of [product] and called it [product] 2007. So what's the excuse for the horrific simplicity and mid-90's 'features' that are browser based forms within [product] 2007? Like for example the horrendously simplistic table layout control."
"Yeah yeah yeah - I know that you can always drop to using webparts or full ASPX pages for this stuff but why should you? [product] is a pretty rich tool for forms filling - so why should we be expected the reinvent the wheel when all we want is to fill in forms?"
I found this blog this morning about an hour before my O3 with this developer, so I brought it up during our O3. My comments to him were that if someone from Acme stumbled across his blog, they could begin to question his personal motivation and passion for their products, and they could even request that this developer not be placed on any high profile projects. I also asked him to consider what one of his customers might think if they stumbled across this. For example, our customer could conceivably see this and wonder if they selected the right product stack, because according this blog it seems like there are a lot of bugs and technical challenges built into the product. My attempt was for him to see the situation from the point of view of how this could potentially impact him personally.
His rebuttal, in classic IT techie fashion, was that everything on his blog was technically accurate and in fact his blog demonstrates his abilities to solve complex problems (he has numerous samples of code and descriptions of solutions, and he is in fact a very good developer). My point was that a non-technical reader of his blog wouldn't care about the technical accuracy, but the language he used certainly may raise some eyebrows.
In the end, we didn't see eye to eye. Does anyone have any recommendations as to how I could provide feedback that would encourage him to tone down the overall negative tone of these posts?