Earlier quoted context omitted.
Also do you mind modifying the title to say a Survival Guide to a C.S. PhD? Absolutely everything the GP says is spot on, the C.S. PhD is really atypical amongst all the Ph.D. disciplines. E.g. the resource constraints that exist in many disciplines don't even exist in C.S. - it is almost completely the product of thought/ideas and ever cheapening computing power. I would suggest sending out your article to Ph.D. stu…
I disagree. It's true that it's easier to get funding for CS but the career strategies described are exactly the same for most other fields. Many phd students just can't understand this post though; they think they're 'students' like they were in undergrad but it's whole different ballgame. The concept of the symbiotic relationship between adviser and student for example - most phd students just cannot see that, even…
Freedom to choose the topic: Only to the extent that he could choose the advisor amongst a list of 3-4, which gets narrower after advisor selection
Ownership: I understand the sense in which the author wrote this, so I cannot disagree too much. But my friend would often explain how he could be most productive precisely by being a 'cog in the wheel' in the sense of how much cooperation was required from his lab mates for him to make any amount of reasonable progress
Exclusivity: The exclusivity is true in the sense it is described, but unlike in CS, did not lead to any major benefits (so sort of diminishes the leading statement about the appeal of the PhD). He went through a couple of post-docs, and then eventually landed what was a coveted position in his field - which still pays not very much
Status: This is the only part which I completely agree, and I actually respect non C.S. Ph.D.s all the more for their persistence because there is very rarely an escape hatch.
Personal freedom: Almost 100% not applicable. As I mentioned before, my friend could not make any progress without a ton of cooperation from lab mates, needed to be in the lab usually based on timings of other lab mates.
Maximizing future choice: Nearly every discipline other than CS would disagree with this. If you read stared's story, you get the distinct sense that his choices were maximized because he came into data science (i.e. he didn't feel that way while in his discipline)
Maximizing variance: This is immensely difficult for science Ph.D.s from what I understand, because the process from Bachelors to PhD, and often with a PostDoc or two on the way, is already too long for most of them and takes up their best years. So the statement "You’re young and there’s really no need to rush" is, well, a bit impractical.
I cannot comment on 'Personal Growth' and 'Expertise' - I don't know if you need a PhD for the former, and the latter is wonderful as long as the cost is not exorbitant (this exorbitant cost is common in other disciplines)
If the advice here is widely generalizable, then I would really like to see a few links to PhDs in, e.g. the physical sciences talking about their experiences with similar pleasure.
On the other hand, the stories I heard from my friends who did their Ph.D.s in other disciplines (Chemical Engineering, Mechanical Engg., Civil Engg., Chemistry, Physics to name some I remember) all had very similar patterns in their horror stories of the lack of resources and its impact on their journey.
So, is it at all possible that a CS Ph.D. who worked on an excellent topic (for which karpathy gets my kudos) in an internet-friendly, internet-visible, exploding field of work at a top institute might not paint anything close to the full picture?
True, that is the not the full article. But the best way to be safe is to never get into a fight - don't get into a PhD without understanding what you are signing up for. The section answering the question: "First, should you want to get a PhD?" is not well researched or widely sourced once you consider that Computer Science is not the only discipline in which people get their PhDs. Hence the suggestion to change the title to C.S. Ph.D.