Live data from Hacker News

Applying to PhD Programs in Computer Science (2014) [pdf]

cs.cmu.edu

91–100 of 106 posts

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#91
post #41

For anybody interested in the computer science PhD process, a good complement to the featured article is Philip Guo's "The PhD Grind" [1]. It's a long (115p, but with big text) blow-by-blow account of the author's PhD at Stanford in the late 00s. It's neither sensationalized nor sanitized, and it's weirdly engrossing for an account of PhD research. I read it before starting grad school and I think it helped my "meta"…

Thanks for the recommendation. I'm currently doing a PhD and spent a few years in the corporate world. I've only read a fifth of it (the downfall) and I feel like some of his not so good experiences could actually be easily avoided by anyone with some work experience. Im already accustomed to knowing that half of the time the leader/professor might not actually know what he's doing or get you to do something that's o…

+1, no one has any idea what they're really doing. This lets people suggest random projects, if you keep prodding them. As your username suggests: "it's a trap!"

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#92
post #41

For anybody interested in the computer science PhD process, a good complement to the featured article is Philip Guo's "The PhD Grind" [1]. It's a long (115p, but with big text) blow-by-blow account of the author's PhD at Stanford in the late 00s. It's neither sensationalized nor sanitized, and it's weirdly engrossing for an account of PhD research. I read it before starting grad school and I think it helped my "meta"…

Well what's interesting is that in the end he did become a prof, so perhaps it should be updated

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#93
post #52

> Some people never do research again after completing a Ph.D. For such people, the Ph.D. was largely a waste of time. Is it? Some of my friends went on to start successful companies after getting their PhDs. I'm a bit envious of them actually, I didn't have that option as my research was on an obscure topic with zero commercial potential. > The Ph.D. is a tremendous opportunity. You get to pick an advisor in any res…

> Some people never do research again after completing a Ph.D. For such people, the Ph.D. was largely a waste of time. This statement reflects the writers' large ego, not reality. It's a shame how this point of view is prominent in the scientific community. I've seen similar rude statements from academic scientists who say that working in R&D at a corporation isn't "real science".

I think the intention was referring to people who do no further research, whether academic or private (e.g. repetitive work with significant exploration involved). The last paragraph of section 2.6 is about doing research work in private companies, no?

I agree with the author that there is little value in doing a PhD if you don't intend to keep doing some form of research afterwards. There are alternative programs or work that would be much more applicable.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#94
post #3

Most Comp Sci PhDs work from home anyways once they’re in.

If by work from home you mean live from the office then yeah, sure :)

Other than experiments that require custom ICs or embedded boards, most CS/CE research can be done from home. Can remote shell into your machine at work, or log into the supervisor's private VM cloud.

It's become much easier than it used to be. Even a decade ago, this was the norm and most of my colleagues were chippies. Even reams of data could be carried via a couple of spinning rust HDs in a backpack.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#95

Earlier quoted context omitted.

I was in this situation, decades ago, and indeed was turned down by CMU. At least back then, CMU like some other elite schools had no MSCS, making it even harder to make the grade coming from Podunk U. My strategy, which worked out okay, was to "bracket" the field by choosing a couple of schools that looked solid and had very large MS class sizes and to just view my "elite" apps as lottery tickets unlikely to pay off…

I think this is bad advice for most people. "An excellent advisor at Mississippi State will do you far more good than a crappy one at Stanford. And will probably cost a lot less." I applied to 6 schools - doing the "bracketing" thing (CMU+UCB as "reach" schools, Wisconsin-Madison & Washington as "mid" schools and Columbia and U Colorado Boulder as safety schools). I got into everywhere but UCB and Washington, but CMU…

All worth considering, yes. I don't envy anyone having to plan a strategy on this.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#96

Earlier quoted context omitted.

easiest way to jump tiers is networking i.e. person to person conversations with PIs. if you're able to represent yourself well and describe your own research articulately and authoritatively it'll make up for a great deal of the gap between you and students from "elite" schools. unfortunately this networking happens at conferences which less resource-rich schools can't afford to send undergrads to. my hack: when you…

> this has worked for me no less than 3 times and led to 2 admissions. I did this when pursuing undergrad research - I didn’t think this would help in grad school admissions. Was this during undergrad or after?

Grad. In undergrad I had less than zero clue.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#97
post #89
post #13

Very interested in working through the PhD as a mid-career SW engineer with a MS. Curious how someone in that state would be seen by the acceptance committee, or, alternatively, by hiring committees post-graduation. Perspectives?

Not positive about hiring committees but I think most would be very open and judge you fairly. It won't be easy to get into a good PhD program, even with prior master's research experience. Did you get and keep old recommendation letters from your master's? That would be helpful. You could throw your application out there, but if not successful, a way forward is to identify a research area or problem, start reading p…

>. Did you get and keep old recommendation letters from your master's?

Let's go with _nah_: at this point they'd be almost a decade old. It would be a measurement that is almost irrelevant to who I am today and my experience. I'm sure I can swing managerial recommendations etc, and it's not out of the equation that, at least at the local level, I could do some interesting volunteer work at the local U.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#98
> As in all of life, you will be most successful if you simply figure out what skills your advisor has that you don’t and work hard at picking up all of those skills without complaining

Which probably means you will pick up programming, as the field moves so fast that professors usually have out-of-date skills. With a younger professor, this may be different.

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#99
post #97
post #89

Earlier quoted context omitted.

Not positive about hiring committees but I think most would be very open and judge you fairly. It won't be easy to get into a good PhD program, even with prior master's research experience. Did you get and keep old recommendation letters from your master's? That would be helpful. You could throw your application out there, but if not successful, a way forward is to identify a research area or problem, start reading p…

>. Did you get and keep old recommendation letters from your master's? Let's go with _nah_: at this point they'd be almost a decade old. It would be a measurement that is almost irrelevant to who I am today and my experience. I'm sure I can swing managerial recommendations etc, and it's not out of the equation that, at least at the local level, I could do some interesting volunteer work at the local U.

Remote collaboration is very common so I would email the best matches (once you’ve one background research) wherever in the world they are!

Re: Applying to PhD Programs in Computer Science (2014) [pdf]

#100
post #61

Earlier quoted context omitted.

Eh, not everything has to measured by how much money you accumulated.

That's not the point. Let's say you spend 6 years in grad school on a stipend of $35k per year. You think you are being paid to get a PhD, but that's just because you are ignoring opportunity cost. If you took your talents to industry instead, let's estimate an entry-level salary. I will intentionally make it lower than average. Let's say $100k per year, which is on the low end in Silicon Valley for an entry-level en…

>Would you pay $390k for a PhD?

Yes, of course, even if you increased it to $800k.

Several thousand brilliant people make this decision every year. Think of it as paying $390k to buy 5-6 years of time, and it starts to sound very different.

5-6 years of time at the prime of your life where your basic needs are taken care of without any enforceable expectations from you.

You can go sit in any of the hundreds of interesting things being taught around you. You can pursue hobbies, go camping in the middle of the week.

If you are lucky, you get to work on interesting bleeding edge projects which may or may not make business sense. For this you get nearly any resource you ask for. Labs in good universities are rather well funded. Supercomputer time to run a random program, easy! Also, most companies are happy to hand out huge amounts of cloud credit, reference hardware.

Compared to making 390k, are you surprised that at least some people would make this decision? Also, 35K per year + well paid internships (~40$k for a summer) is a rather comfortable amount of money for a 25 year old person in most situations.

Post reply on HN