Before I over post here (really got me thinking on the journey home though) one more thing ...
The description of wanting to go back to coding is laced with guilt and uncertainty - and we have all felt it. But it reminds me of Ricardo's theory of comparative advantage - if coding is what you are best at, you should code even if you can do other things (like recruitment) better than some others.
So yes, go back to coding, get a feel for the boat thrumming over the waves again, listen to people's problems in the only way that matters - by sharing them. Your authority is useful but it is not what makes a good CTO else every idiot would be a good one. You aren't supposed to know the answers - enjoy the journey of discovery and speak not because you think you the CTO should weigh in, but because you the hacker feels it.
Ok, Time to stop pontificating, that's enough posts on one thread:-)
The description of wanting to go back to coding is laced with guilt and uncertainty - and we have all felt it. But it reminds me of Ricardo's theory of comparative advantage - if coding is what you are best at, you should code even if you can do other things (like recruitment) better than some others.
So yes, go back to coding, get a feel for the boat thrumming over the waves again, listen to people's problems in the only way that matters - by sharing them. Your authority is useful but it is not what makes a good CTO else every idiot would be a good one. You aren't supposed to know the answers - enjoy the journey of discovery and speak not because you think you the CTO should weigh in, but because you the hacker feels it.
Ok, Time to stop pontificating, that's enough posts on one thread:-)