41–50 of 99 posts
Earlier quoted context omitted.
Usually Masters degrees require Bachelors first. Maybe you mean Associates?
Some programs in Canada allow you to get a masters in CS without having a CS background. It would require taking certain prerequesites.
I'd highly recommend you at least try it for a while so you'd understand what you'll be passing on. One thing that isn't worth it is regretting down the line that you didn't go and having neither an understanding of what you passed on or a good reason why you did it. You don't even need to go to a 4-year college: take some Community College classes if you're unsure or money is an issue. (if you're careful to take classes that transfer, you can eliminate a big chunk of the cost if you decide to go for the degree) The downside is that 2-year schools really don't give you the same experience as the 4+-year schools. Bonus points if you take classes while trying to carve your own path: it's hard but then you'll get the experience from both sides to inform your decision.
I also made some of my best life-long friends, and now business partner, in college. As you can see going to college is more than just the degree.
As others also mentioned having a degree significantly improves your chances of getting a programming job. I’ve helped many people prep for job interviews, both with and without a degree, there is a stark difference for better or worse.
I’m not saying college is a must-have. But I’m saying it can be a life changing and amazing experience, that is way deeper than just studying computer science.
I still reflect on those nostalgic days sitting in the coffee shop or student union on campus discussing math, philosophy, politics, programming with numerous people, many smarter or more knowledgeable than myself. I feel that I had a major “awakening” in college. :)
Both. Do not expect a college to teach you how to write good code; they won't. You can write terrible code and still get Cs/Bs. ("Cs get degrees") It's up to you to learn how to write good code. If you want to progress in your career, you will need to be able to write good, maintainable code, and that isn't a skill that's taught in college. If you're "that guy" on the team that writes shitty code, sure, you'll get a…
With a non-CS degree it may be a little harder to get an interview, but if you can interview well, it's not going to count much against you. A degree in a strong technical field (like Physics or Engineering) might even count in your favor compared to a CS degree if you can still do well on an interview.
With no degree at all, you may find it harder to get interviews in the first place. There are definitely still jobs to be had, and companies who will interview you, but the options will, at least initially, be more limited.
I'm 31 and considering getting a degree. Wondering if I should go for a masters in CS or do a bachelor's. Coming from a non-cs background and doing a career change at this point isn't easy. Master's would be much shorter and the Bachelor's obviously would take much longer. Any suggestions?
Usually Masters degrees require Bachelors first. Maybe you mean Associates?
I'm 31 and considering getting a degree. Wondering if I should go for a masters in CS or do a bachelor's. Coming from a non-cs background and doing a career change at this point isn't easy. Master's would be much shorter and the Bachelor's obviously would take much longer. Any suggestions?
That strongly depends on what you plan to do with it once you have it. Is it just for the credential? Is there some specific area of knowledge you feel you need to know to advance your career? Is it for the sake of personal curiosity?
If you actually want to lean something, you have to check some available lit and see if you actually care about the problems CS people are trying to solve. Just because CS has something vague to do with all things Valley, programming, six-figure salary, hacking the Matrix and other shiny stuff doesn't mean you're gonna like it or end up valuing it.