There's a certain snobbery about people who had their act together. Not everyone knew what they wanted to do as an undergrad. You might have more aptitude than people with a BS CS. Pick a program that doesn't treat you as a cash-cow: one where you can take the same courses as undergraduates and PhD students. Then ignore nay-sayers.
If it's a two-year program, you can likely get enough courses in to learn something serious. I have less respect for one-year BS/MS masters programs simply because you won't be taking that much. In two years, you could take 12-16 courses and maybe do some research in the second year.
When it comes to university credentials, people like to "lock-in" their value. If you went to Harvard, no matter how much of a failure you turn out to be, you went to Harvard and people should respect you. So, if I have a BSCS, there's a great temptation to say, "no, you can't go back in time and get to the same level as me. Even if I'm incompetent at my job, employers should devalue you no matter how good you are because you're that 'absolute lowest form of life in software engineering'". But we shouldn't think that way. You're trying to better yourself. Kudos!
To be realistic, you might come out of the program not on-par with the type of student that would be capable of applying to top PhD programs, depending on how rigorous your courses are. Two years can be a short time, especially if you're starting with intro to programming. However, if it's a good program, I think you can come out well among those looking for software engineering jobs.
The real issue is that the BS degree covers (roughly) 2 years of general study and 2 years in a major. Anyone that has already done the general study part just wants to do the 2 years part in another field. I think it is a failure of the academic system (in the US) to not break down the degrees correctly and to call those 2 years in another field an MS--should be a 2nd BS.
I will note that in Europe, a lot of the general study that US universities do in the first 2 years of a BS are done in the last two years of high school, for example the French baccalaureat (bac).
I ended up taking some post-bac courses at the university I'd gone to for my BA then going directly into an MS program.
1. Getting re-admitted to ones alma mater is simpler than a new school (given that these are adults going back to school who may well have moved and established families, their alma mater quite possibly is no longer an option)
2. How many credits were waived? This is a pretty serious sticking point, as anything > 2 year full time equivalent becomes a major time commitment & investment. I would also point out here that this can vary significantly by institution, unfortunately.
3. Many undergrad classes don't support a fully flex part time schedule (or, severely limit their evening & part time options). This becomes increasingly important in this scenario.
While there may or may not be an admission-department policy or stigma against second undergrad degrees, the system is by and large certainly not geared to encourage it as of present.
But the question here is what is best for the poster.
Assuming he can pass the MS degree, a future employer will give much more credit to an MS than a second BS in CS. Furthermore, as he describes it, the coursework already includes the equivalent of an undergrad in CS or more.
source = me. i'm currently admitted back to my alma mater for a second degree in CSC and will be returning in fall this year.
If you have that kind of passion for software development, you'll do fine, regardless of your original degree (or lack thereof). Having said that, I'm skeptical of the value of a MS in CS without a BS in CS. In my MS program, the assumption was that you had the basics - algorithms, data structures, language theory, basic hardware design & logic, compiler design. You can certainly gain that knowledge with enough reading on your own, or taking some courses at a local community college to get the basics.
Would you mind if I email you a few follow up questions?
So the real questions is: can you handle the coursework?
Only you can answer that. If you can pass the degree, and it is from a decent school, I don't see how it could fail to be worth it.
No, definitely not a waste, but I'm not sure it's an optimal use of those resources. You can try to simply do the minimum to "get your foot in the door" of software development jobs, then take it from there. That minimum is probably taking mostly programming-oriented courses, and asking your programmer friends what else can you study to make you a more appealing candidate. (Not sure I'm qualified to give that advice, but feel free to contact me about that if you want)
If this option is available to you then I'd heartily recommend it.
No employer has ever asked me for a github address, or a list of open source commits. I put github on my CV via a goo.gl url last time, and counted very few visits. Yet they invited me for interview.
HR filter by qualifications, and hiring managers filter before phone screen on what you claim in your CV. Then they assess at the interview whether you were lieing.
If you were genuinely famous in the OS community, or had spent a year full time making an amazing product they could see, I think things would be different. For most software engineers, 80% of our work is for our employer. I've made some awesome stuff for other people. It's not on github. My boss wouldn't like that.
Is the above really a good recommendation? I'd say at least the MS would get him through the HR filter?
Then after that, HR appear to filter by previous job title, hoping to see career progression and a similar title previously.
I guess the people at a large company that reduce 200 resumes down to 20, before the hiring mangers sees them, do not understand Ruby. They understand that they must be able to quantify why they rejected an applicant in case of a lawsuit. Hence the frustrating rigidness.
While I understand, respect and even agree with the reason why - the fact remains that I studied Communication, Beer and Skirts for my undergrad degree, didn't start programming until two years ago when I was 30 and now more than anything in the World want to be a software engineer.
So for somebody like me - the absolute lowest form of life in software engineering - is spending two years doing a coursework only MS CS (first year is a fast paced BS CS) a waste of my time and money?