If your VP isn't trusting his technical directors to make appropriate choices when producing quality reliable software and infrastructure then I would say that is a problem with company culture.
I wouldn't have a problem selling the technical merits of a highly consistent database to a technical director. So everything else is moot to me.
I agree about the "bug" association, that is a negative stigma that I could see attached to it- but there are plenty of projects who have stupid names which pass by unnoticed.
take distro release names; Beefy Miracle.. Wheezy.. Natty Narwahl.
And these terms are used internally too. "Oh, that machine was running Squeeze and not Jessie which is why we can't install the latest gdb" etc;
You're giving this much more credence than it will have in real life.
I wouldn't have a problem selling the technical merits of a highly consistent database to a technical director. So everything else is moot to me.
I agree about the "bug" association, that is a negative stigma that I could see attached to it- but there are plenty of projects who have stupid names which pass by unnoticed.
take distro release names; Beefy Miracle.. Wheezy.. Natty Narwahl.
And these terms are used internally too. "Oh, that machine was running Squeeze and not Jessie which is why we can't install the latest gdb" etc;
You're giving this much more credence than it will have in real life.