>You might argue that, but I don't think the argument would be on solid footing. The position requires a foot in the marketing world and the technical world. Re-read Ken's original post and it will be abuntantly clear what Ken's role, and more generically, what the role of the Fox PM is.

I think you misunderstood my post. I'm simply stating that Ken's job is not to fix bugs, or develop features. He won't be *directly* responsible for fewer bugs and more stability, because it's not his job.

Ken is responsible for working with the marketing teams, MSDN, and the product website. There's no doubt that he'll have his nose other places in the product, suggesting features and fixes, but I don't believe he'll be spending a significant chunk of time developing them.

Ken's return to VFP may be indirectly responsible for fewer bugs and greater stability, perhaps by re-energizing the team, but I hesitate to put the responsibility for fewer bugs on Ken's head, and won't take away the credit the dev team should get when it happens.

All in all, there's no doubt that Ken's return is good news.

Daryl