As someone who is a safe distance from the C Suite but has worked with many and varied over the years, I would much rather have somebody at that level who lacks some of the technical skills but has justified trust in the people who he puts beneath him, but knows how to handle the rest of the board and manage people. Those have been the ones I've considered good.
I've worked with plenty of C level guys who are far better at the technical roles than I am, and they get mired in the weeds, lose the big picture, and fail to bat away all the BS coming from the board and foster a hideous work culture while standing over your shoulder saying "Do this thing this way, actually just let me do it".
The good ones are hardly ever there, because they're constantly pushing your agenda at the board, dealing with the many and varied HR issues that plague most good IT departments (because lets be honest, we're not typically the best "people-people", and making sure everything we suggest as important is put forward as their view and a redline so it gets through even when it's difficult.
Technical Skills / Leadership Skills / Management Skills are not one and the same.
So with respect, I disagree. As a humble lead engineer ;)
Well, I partially disagree, I definitely agree that there's a place where they should at least understand what it is their team is trying to do and be willing to put the time in to learn where it is relevant.
It's like a ship, the captain knows how the engines work, the rules of the sea, and how to navigate. But he doesn't steer the ship, fix the engines, and empty the toilets, he's busy making sure all those teams work together and don't step on each others toes. Or he should be.