Wasting my time/money with a masters after years in industry?
My background: I’m currently working in industry with 4 years of experience doing fairly standard software engineering/web-dev stuff at a couple of different startups. I’ve progressed through the ranks pretty quickly and have a pretty inflated title partially due to the nature of the startup industry. My undergrad is in CS from a top-10 liberal arts school that isn’t particularly well-known for CS, but I found the courses pretty rigorous even if cutting-edge classes weren’t offered. While I still like working with computers and software I’m getting a little burned out by the software engineering world. My goal with a masters was to try and break into more work with AI/ML and CV or try and land a job at a research-oriented institution where jobs seem to be gated by MS requirements. I also happen to like school and thought going back and taking more courses that I couldn’t get to during undergrad would be fun and interesting.
I was accepted and going to be starting the University of Chicago’s MPCS program part-time while I continue my job, but now I feel like I was misguided by the advice I got when I was applying. I knew going in that this was a professional-oriented masters but it seems like this program is target more towards people who want to change careers rather than people like me, so I feel like I may be really overqualified and wasting my time and money. Does anyone have experience with this program in particular or masters programs in general that could offer me some advice? Thanks all!
Posted Sep 26, 2019, 2:26 PM UTC
The best advice I was given during college: "Don't get a masters in what you already do"
So I swapped it up and now I'm finishing up my MSSE so I have a breadth of experience for my company to use.
On the flipside, I am wrapping up a MS in in CS, and it has expanded my knowledge in areas that I didn't get exposed to previously.
An MS in most topics will of course expand your knowledge in a limited subset. I’m only stating that by exposing ones self to another topic, their toolset is vastly expanded rather than only enhancing a specific tool.
Consider the tool analogy to be your BSCS is your socket wrench, and your MSCS is an extended torque wrench. Now you know exactly how much ft-lb you’re applying, but the problem set didn’t change as it’s still a socket. Obtaining an MS outside your tool set expands your belt to say a screwdriver set, or a nail gun, or a table saw, etc.
Now not only can I effectively design a system using solidified SE principles and practices, but I can also implement said system; or I can even take on a managerial/architecture role for a system of systems and help developers since my core foundation is CS. In my eyes that has more value then an MSCS where I may become better with spatial structures or optimized doubly-linked-lists.
What was your background before entering the MS?
BS in CS, BA in Theatre. I double majored in underground. Also had 10 years in industry before returning to school.
Interesting... your background is similar to mine albeit with much more industry experience than I have. Did you do a more professional-oriented MS or was it very research-based?