> I'm of the general mindset that the CTO should be the most technical. For a decent size company I'd hope the same, but with the proviso that over time any sp

> I'm of the general mindset that the CTO should be the most technical. For a decent size company I'd hope the same, but with the proviso that over time any specific industry experience will degrade to a more general understanding, which is fine. And if they don't have the experience they delegate. So bearing in mind the original story, either the CTO should be at least decently technical enough to avoid composing SQL like that commit does, or the CTO should not be committing code in the first place.