Are there misconceptions with what a CTO actually entails? I've not heard of a CTO that does any physical programming with respect to their job. This might be different in a small startup but my understanding of a CTO's role is to guide architectural and development goals of the company as a whole - and to hire great people to implement that vision. It sucks he would have to leave but part of me wonders why he thought the CTO role involved a fair amount of programming and why he wouldn't just move into a lead developer role as opposed to leaving entirely?
At HelloWallet, our CTO does indeed do some programming some of the time. Since we are still somewhat a bootstrapped startup, everyone that has the ability to help out does at some point. Is it the overwhelming amount of time? Well, no, but still...
In regard to architectural and developmental goals, that job is the responsibility of our Chief Architect...who also does a very substantial amount of programming as well.
TLDR; Titles are not always one-to-one with roles.
