[dc2447]

Twenty plus 1-1s, means twenty plus direct reports.

No wonder the guy was burnt out. That number is simply not manageable in any worthwile way.

The rest of the article just reads like someone is CTO purely because when he joined.

The friction with the VP in terms of how the VP executed hints at someone a little out of there depth maybe.

[peteretep]

    > The rest of the article just reads like someone is CTO     
    > purely because when he joined.

I disagree. I joined my last role as CTO in a slightly bigger team, taking over from someone who hadn't put in a very good structure. I found the article to be thoughtful and insightful, having gone in to it with the suspicion it was going to be another CTO at a 7 person company self-aggrandising.

    > The friction with the VP in terms of how the VP executed
    > hints at someone a little out of there depth maybe.

If you're not out of your depth at least a little bit in your role, then it's probably time to be looking for a promotion. If you're a pure developer (and want to stay that way) it's time to find some harder problems, and if you've segued in to management, it's time to start thinking about how to do your boss's role.

[dberg]

> If you're not out of your depth at least a little bit in your role, then it's probably time to be looking for a promotion. If you're a pure developer (and want to stay that way) it's time to find some harder problems, and if you've segued in to management, it's time to start thinking about how to do your boss's role.

Very well said, I think complacency is killer and thinking about how much you need to challenge yourself to move up the ranks is always a good think to reflect on.