daveyrocket said:
It was for me too, when I got it. But after that it felt like a hollow, costly victory. The importance of the PhD for me eroded especially quickly when it came time to looking for jobs and realizing how badly I had dropped the ball by choosing physics.
For me, getting a Ph.D. was to finish off a family curse. Due to some reasons beyond his control, my father was unable to finish his Ph.D., which meant that it was planned that I'd finish mine. The weird thing was that I didn't realize that this was the plan until long after I got my Ph.D., my father had passed away, and I was looking at some old letters.
But because of my environment, whether I got a job is irrelevant. I got the Ph.D. and therefore could declare victory.
I didn't. But I was a pretty good programmer when I went into my PhD. And my skills developed some, mostly because of doing things in my spare time that had nothing to do with physics. But thanks to physics, I learned that numerical programming is nearly as boring and annoying as web development.
I actually find numerical programming soothing and relaxing. This is one reason that I get paid large amounts of money. It's a supply and demand thing, and the number of people that can spend a month debugging several thousand lines of badly written optimization code to find out that there is one line that needs to be changed isn't huge.
This is why software/finance firms hire physics Ph.D.'s. It's assumed that if you have a physics Ph.D., you don't hate numerical programming and you are willing to do it 60 hours a week and spend weeks tracking down bugs. If this isn't true, then you have a problem.
Of course, if I had gone into programming, I'd have spent 40 hours a week professionally doing it for 8 years and I'd be much more abreast of current technologies, etc.
For numerical stuff there latest technologies involve multi-core and GPU. Multi-core/GPU/cloud computing requires that a ton of programs be totally rewritten. Which is cool. Also, what's really, really cool is that we are increasing compute power by 1000x. Right now we are just using the new tech with old systems and processes. There's got to be a way of doing stuff that we didn't imagine before.
If you do that with physics, nearly every job that comes up that isn't academic comes up because it's asking for a degree in "engineering, physics, chemistry, or related field." Nearly every industrial job a physicist can do, an engineer can do, and the engineers also ave a boatload of jobs that are 'closer to home,' so to speak.
That's not true. One problem is that the jobs that are specially tailored to Ph.D.'s tend to be clustered in a small number of places. If you go into any major city, you'll find jobs for mechanical engineers. The jobs for astrophysics Ph.D.'s are clustered in only a few cities. For finance, it's NYC. For oil/gas, it's Houston. For defense, it's Los Alamos/Oak Ridge.
Also, I don't think that the supply/demand is that different. There are a lot more jobs for engineers, but there are a lot more engineers.
Especially when you consider the type of programming you do in physics sucks nearly as bad as web development.
If you hate physics programming, you are going to have a terrible, terrible time finding jobs in industry. If you go into an interview for most theoretical physics Ph.D. jobs, and the interviewer senses that you hate numerical programming, then game over. You can fake liking programming, but if you can fake not hating numerical programming then you can't hate it that much.
Something that has helped me a lot is that when someone mentions C++, my eyes light up, and I can talk your ear off about the limitations of template meta-programming in numerical code. Faking interest is impossible, because if you can fake interest that means that you are interested.
Of course having my PhD in physics is better than having spent that time in jail, but if I had gone into software (or any other field) after my BS or MS then I'd have 7-8 years of experience in the field, a network of contacts in the industry, I'd probably be able to afford a car that isn't 20 years old (1991 Toyota Corolla LE, baby!) and I might even own a house instead of having spent years living in crappy one bedroom apartments. A PhD doesn't compare to that.
I managed to get most of that with my Ph.D. Also, the reason I get $$$$ is that the number of people that can tolerate working for large periods of time on nasty numerical code is rather small. You can hand me six pages of greek equations, ten thousand lines of badly written code, and give me a few days, and I'll find the problem.
In every software company, I've worked at most programming ends up being extremely tedious debugging, and if you can't stand that, then I really don't see how you are going to survive in that world. If you go into an interview, and the interviewer senses that you can't tolerate painful debugging, you aren't going to get the job.
One other thing. I try to keep my expenses low. Doing Black-Scholes is okay, but my heart is really in stuff like numerical relativity and supernova models. The lower my expenses, the more money I have in the bank, and the sooner I can quit and go back to being a graduate student. I've worked out the numbers, and I figure that I should be able to go back into astrophysics within the next decade.
I felt that way when I got into the PhD program. But years of working on complicated but useless projects that no one outside a small circle of academics will ever care about has slowly and painfully crushed that feeling.
Some of that is sales and marketing. Why should a Wall Street bank care about neutrino radiation hydrodynamics. Well... This is the equation for multigroup flux limited diffusion. This is the black scholes equation with Heston local volatility. Looks the same. Now consider that there are tens of billions of dollars of transactions that depend on solving the latter equation in near real time.
Got your attention? Also one fun thing is that people in finance are *extremely* concerned about round off errors, so you get into huge esoteric discussions about hardware floating point handling. The reason is that the sums of money are large enough so that a "round off error" could end up being several million dollars. I've been in situations where I've had to spend two to three months tracking down a round off error so that we could put new code into production. It's painful and ugly, and 99% of the people in the world will go insane rather than doing that sort of thing, but that's why physics Ph.D.'s get hired.
If you don't care, what can I do to make you care? If it doesn't seem important, what can I to to make it important?
I don't enjoy physics any more and I doubt I ever will, and I certainly will never look back at my experience in graduate school with anything but contempt.
The worst thing about graduate school was that it ended, and the best thing about my current job is that it feels a lot like graduate school with more money. One thing that makes it similar is the moments of glory. You spend weeks tracking down this one bug, and it's driving you insane. Finally, you think you got it. You keep your hopes down because this is the sixth thing that you tried. You do something ridiculously tiny like changing a >= to a >. You run the compiler, crank up the test harness, and it works. You try a few more things, and you got it. So you savor the moment, and those two minutes when you know you've got it makes the previous weeks of pain worthwhile.
Then you cross off one bug, make a note on the "things to remember when you write your self-evaluation at the end of the year" and move to the next bug... :-) :-) :-)