If you are at CTO rank and were previously an engineer, then you've already accomplished your goal and know interruptions on a constant basis are part of the jo

If you are at CTO rank and were previously an engineer, then you've already accomplished your goal and know interruptions on a constant basis are part of the job. That was my argument. Your rebuttal is a straw man: I make no claims as to what the role of a CTO is or in what way it differs from a software development role. Simply that, if you are a software developer and have aspirations to become a CTO, you have more skills to develop than technical skills that are only effective in a perfectly isolated setting.