>I might argue that Ken's position is not one that will lead directly to fewer bugs. Rather, his position is one that should lead to a product that is more "widely respected." After all, his position is a marketing position, not development.
>

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.


>Don't get me wrong. Ken's return to the product and his boundless energy for and love of Visual Foxpro will lead to only good things. There's no doubt that his return will bring a renewed enthusiasm to the team. That in itself will be good for the product, from a development standpoint.
>

Right, and what is good for the product from a developer standpoint is one that is less buggy, more stable, and has an evolving feature set...