Live data from Hacker News

The Ph.D Bust: America's Awful Market for Young Scientists

theatlantic.com

121–122 of 122 posts

Re: The Ph.D Bust: America's Awful Market for Young Scientists

#121
post #61

Earlier quoted context omitted.

Writing a grant proposal is about as hard as writing a paper. So if they apply for three grants and also write three papers in a year, then yeah - that's 50%.

Getting a grant proposal accepted is much more difficult than getting a paper accepted.

I don't think that's a valid generalization. It depends enormously on the funding agency and the place you're submitting the paper, respectively.

You're not going to be able to do a good grant proposal unless you have a good track record of research, with multiple papers. So in that sense, a grant proposal supersedes a single paper.

But, given that you've already done all those papers, a grant proposal is just writing, not new research, so it should actually be massively less work than doing all the original research that goes into a paper.

Re: The Ph.D Bust: America's Awful Market for Young Scientists

#122

Awareness of the opportunity cost and likely outcomes has been hitting me hard lately as I consider dropping out of my top-5 science (not CS) program 2 years in. I've gotten to a comfortable place with python/numpy/matplotlib and am wondering how hard it would be to break into web development as somebody who has only programmed in a scientific setting. Besides Python, I also know enough R and statistics to build line…

I did it. I did a Master's (never had any intention of a PhD) in engineering, mostly focused on OR decision making applications in geography. So I knew maps and could write Matlab and Python scripts and I'd played around with some C/C++. I progressed into a tech career starting with a place where the mapping & geography knowledge was a huge asset. My CS experience was limited to 2 undergrad courses and reading a few books. It's taken a few jobs since then and about 5 years but I'm definitely purely a software developer now. Two things that I think helped were having a technical bachelor's degree (even though it's not CS) and having some projects I could talk about that that meant I knew stuff about the company's products that CS students wouldn't tend to know, like mapping projections and norms in GIS. When they asked me questions about stuff like sorting algorithms, I could explain some assumptions I would make based on the kind of work they do, not just give the generic 1st year CS course answer. Dev Bootcamp or similar might be worthwhile to give you some buzzwords for your resume and some projects you can show off. If you can get those on your own or your experience buzzwords match what you see in job postings, then it's probably not worthwhile. I wouldn't put the bootcamp on my resume, I'd put the skills and projects it got me down as personal interest projects.
Post reply on HN