Never do a PhD for the money. Ever. It's not worth it, compared to using your skills to get a good education BSc / MSc and then start your career. You miss so many years of good income, plus income growth and will always stand out as the theoretical type. That being said: it's all about curiosity and people. So if you're curious and have the time / money... go for a PhD!
I know of three PhD's in comp sci that went straight into Goldman Sachs (and one hedge fund) where they immediately started earning far more than those of us that left Uni with our Bachelors. They work in high frequency trading mainly using Java.
Why (Not) Do a PhD in Computer Science?
11–20 of 45 posts
Re: Why (Not) Do a PhD in Computer Science?
#12Never do a PhD for the money. Ever. It's not worth it, compared to using your skills to get a good education BSc / MSc and then start your career. You miss so many years of good income, plus income growth and will always stand out as the theoretical type. That being said: it's all about curiosity and people. So if you're curious and have the time / money... go for a PhD!
I know of three PhD's in comp sci that went straight into Goldman Sachs (and one hedge fund) where they immediately started earning far more than those of us that left Uni with our Bachelors. They work in high frequency trading mainly using Java.
Re: Why (Not) Do a PhD in Computer Science?
#13Earlier quoted context omitted.
I know of three PhD's in comp sci that went straight into Goldman Sachs (and one hedge fund) where they immediately started earning far more than those of us that left Uni with our Bachelors. They work in high frequency trading mainly using Java.
Interesting. I wouldn't have though Java was suitable for HFT due to garbage collection pauses playing havoc with your system determinism and performance reliability. I supported a derivatives trading system written in java that was canned due to performance issues, and where I am now we had java FIX protocol gateways that we've replaced with C++ components, again for performance reasons. I'm not saying java has perf…
AFAIK, mark-and-sweep GC was removed from the JVM years ago (except on Android, where Dalvik used it until 2.something). I can't help with the rest of your post though.
Re: Why (Not) Do a PhD in Computer Science?
#14I like the reasons described in the post. I would like to add one more that was really important for me when deciding to do a PhD in CS - learning to write papers. While it may seem like a burden for some people, I think that describing your research in a very limited space (something like 8 pages) teaches you very valuable skills. You should also write it in a way that most of the readers will understand your ideas…
Re: Why (Not) Do a PhD in Computer Science?
#15I like the reasons described in the post. I would like to add one more that was really important for me when deciding to do a PhD in CS - learning to write papers. While it may seem like a burden for some people, I think that describing your research in a very limited space (something like 8 pages) teaches you very valuable skills. You should also write it in a way that most of the readers will understand your ideas…
This is important to me. It is the reason that most of the jobs I am interested in require a PhD. Outside of the start-up and web space, there are actually a lot of industrial research jobs that will not even give your resume the time of day without a PhD because you are expected to produce technical literature and patents. I thought it was kind of funny in the article how they still mentioned the "I want to be a pro…
Do industrial research labs really employ freshly minted PhDs - who probably haven't acquired the most important skill in modern research: the politics of attracting funding/backing?
Re: Why (Not) Do a PhD in Computer Science?
#16Earlier quoted context omitted.
This is important to me. It is the reason that most of the jobs I am interested in require a PhD. Outside of the start-up and web space, there are actually a lot of industrial research jobs that will not even give your resume the time of day without a PhD because you are expected to produce technical literature and patents. I thought it was kind of funny in the article how they still mentioned the "I want to be a pro…
Don't those kinds of industrial research jobs also usually require the kind of publication track record that you have to acquire in academia to survice? Do industrial research labs really employ freshly minted PhDs - who probably haven't acquired the most important skill in modern research: the politics of attracting funding/backing?
Re: Why (Not) Do a PhD in Computer Science?
#17Earlier quoted context omitted.
This is important to me. It is the reason that most of the jobs I am interested in require a PhD. Outside of the start-up and web space, there are actually a lot of industrial research jobs that will not even give your resume the time of day without a PhD because you are expected to produce technical literature and patents. I thought it was kind of funny in the article how they still mentioned the "I want to be a pro…
Don't those kinds of industrial research jobs also usually require the kind of publication track record that you have to acquire in academia to survice? Do industrial research labs really employ freshly minted PhDs - who probably haven't acquired the most important skill in modern research: the politics of attracting funding/backing?
Yes.
> Do industrial research labs really employ freshly minted PhDs - who probably haven't acquired the most important skill in modern research: the politics of attracting funding/backing?
Yes. How do you expect freshly minted PhDs to learn the art of attracting funding and backing?
Re: Why (Not) Do a PhD in Computer Science?
#18You need to be aware that PhDs often make less or the same income as a "professional" degree holder does (for a higher student loan burden). That means if you feel that the experience will be personally enriching, the fact that it might not be financially enriching may not matter.
2. US professional degrees have dropout rates of 3%, approximately. The Ph.D. with lowest dropout rate, engineering, has a 35% dropout rate. Pretty much everyone who can be admitted to a Ph.D., funded is a guaranteed admit to a pro programme that will on average make them more money.
One should do a Ph.D. if one will not regret it even if one never holds a faculty position, i.e. it's more consumption than investment, or if one got into a TOP programme in one's chosen field. Economics seems to be in the process of collapsing from top 5/6 to top 2, CS has been 4 for a long time, but the principle is the same everywhere.
Re: Why (Not) Do a PhD in Computer Science?
#19However, after careful consideration, I realized that: 1. I am not entirely sure if my enthusiasm will be enough to push me through a PhD 2. You can obtain a great skill set, meet loads of smart people and work on intellectually stimulating problems in industry, too.
That's why I plan to work for some time and then re-evaluate my situation and maybe apply for a PhD, who knows.
Re: Why (Not) Do a PhD in Computer Science?
#20Earlier quoted context omitted.
I know of three PhD's in comp sci that went straight into Goldman Sachs (and one hedge fund) where they immediately started earning far more than those of us that left Uni with our Bachelors. They work in high frequency trading mainly using Java.
Interesting. I wouldn't have though Java was suitable for HFT due to garbage collection pauses playing havoc with your system determinism and performance reliability. I supported a derivatives trading system written in java that was canned due to performance issues, and where I am now we had java FIX protocol gateways that we've replaced with C++ components, again for performance reasons. I'm not saying java has perf…