Why do you say that Carmack is in management? I don't get the impression that he's a people manager. A CTO does not necessarily have people reporting to them in a people management sense. From what I've read, I would assume he does not. (I could be wrong - I don't really know.)
High judgment individual contributors often take on responsibilities that can be considered management, like deciding business and technical strategy, designing products, prioritizing roadmaps, etc., but while these are management functions, taking on these responsibilities does not mean that one is in management.
From the blog post, it sounds like Carmack is a highly productive, high judgment individual contributor with the responsibilities you'd expect of a CTO (technical strategy). I would say that someone is "in management" when their chief function is managing other people. From this post, Carmack seems to be delivering work as an individual contributor and (very senior) technical lead.
Along the same lines, I recommend we discourage phrasing like "move up to management". Management is a different job, not a better or superior one. In well-run technical companies there are managers and individual contributors at all seniority levels, such that one does not need to become a manager to "move up", even to CTO level.
In some of his recent keynotes (especially the later quakecon ones) he focuses a lot on how he's changed his mind and that he now believes that software development has a lot of "social science" aspects to it. I think he's given a lot of consideration to how one manages a software team, and even though he sometimes disappears into his office to write something like this Netflix app, he still does manage people.
Management is a different job, not a better or superior one.
Oh please. Until management is no longer a more profitable career track than staying in engineering, could we stop lying to the younger folks that might believe the nonsense they read on HN?
In well-run technical companies there are managers and individual contributors at all seniority levels
Non-management contributors with C-suite pay (and occasionally titles), are still rare enough to be noteworthy. Unless they're on par in compensation and control of the company, pretending traditional corporate management doesn't consider themselves their superiors is just ego-stroking the engineers too dumb to be insulted.
>I recommend we discourage phrasing like "move up to management".
Word. At Etsy, we'd occasionally call out people (in a friendly way) for saying "I got a promotion to manager!" Someone (usually a more senior manager who used to be an IC) would say "not a promotion, lateral move." Drove the point home, at least at an IC level, that management is not a move up.
High judgment individual contributors often take on responsibilities that can be considered management, like deciding business and technical strategy, designing products, prioritizing roadmaps, etc., but while these are management functions, taking on these responsibilities does not mean that one is in management.
From the blog post, it sounds like Carmack is a highly productive, high judgment individual contributor with the responsibilities you'd expect of a CTO (technical strategy). I would say that someone is "in management" when their chief function is managing other people. From this post, Carmack seems to be delivering work as an individual contributor and (very senior) technical lead.
Along the same lines, I recommend we discourage phrasing like "move up to management". Management is a different job, not a better or superior one. In well-run technical companies there are managers and individual contributors at all seniority levels, such that one does not need to become a manager to "move up", even to CTO level.