3 ms·
> For example, if you ever intend to pursue entrepreneurship or aspire to CTO rank, you can expect to be interrupted often. If you are at CTO rank, your job is
by tensor 10y ago
> For example, if you ever intend to pursue entrepreneurship or aspire to CTO rank, you can expect to be interrupted often.
If you are at CTO rank, your job is not to program. You may still do that at times, or other things that require quiet time, of course. For that, you need "office hours" or "quiet hours." You simply make yourself unavailable and go somewhere you can have uninterrupted time.
If you are trying to be a developer that gets interrupted all the time as a CTO, you are definitely not doing your job right.
- jonaf 10y agoIf 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.