by _mjk on 10/4/17, 1:01 PM with 5 comments
by PaulHoule on 10/4/17, 1:19 PM
As for practitioner, I think you could jump right into a "data science" kind of role. Python is particularly good for that. Maybe also something with embedded systems.
I am not so sure how to switch fields for research. I was discouraged from doing that back in the day.
For background, I got a PhD in theoretical physics at Cornell in 1998. I did a postdoc for 1 year in Dresden, Germany. In school I did as much as I could in Java. I quit physics, went home and bought a farm close to Ithaca (my wife grew up 40 miles away.) She teaches kids to ride horses and since then I have done programming at Cornell, companies in the Ithaca area, remote, as a consultant, etc. I became the black sheep of my research group and I have gone through phases of intense soul-searching from time to time, but I am still here.
by T-A on 10/4/17, 1:19 PM
My guess is that a postdoc would be seen by prospective employers as a clear declaration of intent to stay in academia. But if that is what you want, you should use those few (hopefully!) years to build up a research portfolio which will get you a permanent position. Starting from scratch on something which you have no previous experience with is not the way to do that. I doubt anybody sensible would be willing to let you try on their dime.
If you do not intend to stay in academia, it is time to start revising down the value you assign to certificates of whatever. You are more likely to be asked for an interesting GitHub repo. But if you insist, there is a plethora of things like
https://www.microsoft.com/en-us/learning/certification-overv...
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.ge...
by sevensor on 10/4/17, 1:40 PM
by tmoot on 10/4/17, 5:55 PM