4 ms·
I supervise a couple Ph.D. students working full-time jobs. It's definitely a challenge for them, and it requires immense self-discipline. Coincidentally, I j
by mattmight 16y ago
I supervise a couple Ph.D. students working full-time jobs.
It's definitely a challenge for them, and it requires immense self-discipline.
Coincidentally, I just posted this morning about the three qualities of successful Ph.D. students--perseverance, tenacity and cogency:
http://matt.might.net/articles/successful-phd-students/ http://matt.might.net/articles/successful-phd-students/
The middle part of grad school is generally depressing: you're failing constantly, your work is getting rejected everywhere, and you get consumed with self-doubt.
It's tough to get a Ph.D. part-time because to do it right, it must consume you. Exceptions are rare.
Also, if you're hoping that what you have at the end of a Ph.D. will be ready for end users, you might want to consider that the benchmark for software in academia is "proof of concept." Most academic code is a disaster in terms of usability and maintainability.
The code is so awful that I even drafted a special open source license to encourage academics to release it--the CRAPL:
http://matt.might.net/articles/crapl/ http://matt.might.net/articles/crapl/
- throwaway1 16y agoThanks for the link looks useful. <i>"Also, if you're hoping that what you have at the end of a Ph.D. will be ready for end users..."</i> I have been writing production code for a living for the last 6 years so that doesn't bother me. If other contribute then yes it's likely it wouldn't be production ready. To be honest I don't expect anything that comes out of a phD to be ready for end users without considerable work with a different focus. I think to even get that far will be a great achievement for me. The commitment on top of a full time job is my biggest concern. I think I would be taking quite a lot of leave to concentrate on research full time.