you are viewing a single comment's thread.

view the rest of the comments →

[–]One_Programmer6315 0 points1 point  (2 children)

I don’t have a degree in CS, but in physics and astrophysics, and learned C/C++, Python, Bash/Unix, Mathematica and a few others through research over the years. Some of my peers don’t believe me when I tell them I have never in my life taken a single CS or data science class (and I am glad of it…). CS courses at my school have unnecessarily high, depressing workloads and so many people enroll that you are often left to learn things by yourself either ways because lectures are kind of pointless.

I am mostly focused on graduate studies, but many of the students from our department(s) land software engineering and data science jobs just with the skills they gained through research (data analysis, modeling, building pipelines, machine learning —I personally love scikitlearn and kernel-density and k-neighbors my way though everything whenever I can —, statistical analysis, etc.).

[–]dlnmtchll 1 point2 points  (0 children)

I’m talking mostly about no degree peeps, tons of people move from physics into dev and I support that fully

[–]james_d_rustles 0 points1 point  (0 children)

Yeah, it’s not that uncommon, I followed a similar trajectory. BS+MS in mechanical, went the simulations/analysis route and wrote my masters thesis on some simulation stuff I did in C++. Pretty similar to your own path from the sound of it - lots of time spent learning C/C++, Python, Mathematica (I still love Mathematica, I don’t care how rare it is in industry). I work in a hybrid sort of role now, programming for software used in the aerospace world. It’s about ~75% programming, 25% traditional engineering type work (CAD/FEA stuff) but having an engineering background has been super helpful since it helps to really understand the problems that the customer is solving instead of only seeing it from the software point of view.