"You've always struck me as much more of a mastermind than that; what you like is defining the task, working out what is to be done, and after the interesting problem is solved the actual getting-it-sorted is almost boring by comparison."
No, I don't think that's quite right; I do enjoy a large proportion of the actual doing-the-work phase as well. So I'm not nearly as sure as you seem to be that I'd make a good CTO; my impression of a CTO is that they're quite some distance removed from the actual coalface, would rarely if ever do any coding themself, and would mostly deal with overarching design issues and/or figuring out which of their sub-team-leaders had the most suitable team to be doing any given bit of the upcoming work. Which is precisely where I don't want to be: the people-management side is something I'd like to actively avoid if I can, and while overarching design issues are all very well, I tend to get nervous about my ability to handle them correctly the longer I spend away from actual coding and reminding myself how things really work down at the bottom level.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
No, I don't think that's quite right; I do enjoy a large proportion of the actual doing-the-work phase as well. So I'm not nearly as sure as you seem to be that I'd make a good CTO; my impression of a CTO is that they're quite some distance removed from the actual coalface, would rarely if ever do any coding themself, and would mostly deal with overarching design issues and/or figuring out which of their sub-team-leaders had the most suitable team to be doing any given bit of the upcoming work. Which is precisely where I don't want to be: the people-management side is something I'd like to actively avoid if I can, and while overarching design issues are all very well, I tend to get nervous about my ability to handle them correctly the longer I spend away from actual coding and reminding myself how things really work down at the bottom level.