Live data from Hacker News

The case against CS master's degrees

ozwrites.com

21–30 of 47 posts

Re: The case against CS master's degrees

#21
post #4

I hate to be super-negative, but I'm not even sure a bachelors in CS is a good idea. Oh sure, you learn a few good things along the way, but then the professors start dragging you down their favorite theoretical paths. I'm all for philosophizing and navel gazing, but there's not much practical in things like lambda calculus, NP-completeness and some of the other topics. To make matters worse, these pursuits can confu…

[deleted]

Re: The case against CS master's degrees

#22

Earlier quoted context omitted.

So why not explore a university degree? Let me give you 300,000 reasons-- in other words, the price (in dollars) at a fancy university for said degree. I'm not debating whether anyone should study this. I'm just saying that people who want to get jobs shouldn't need to study it. If you want to do the theoretical stuff, have at it. I'm just saying that it's failed my team as often as it has helped. If the theoretical…

> the dimensions of the problem were such that a quick heuristic did perfectly fine. This is also a theoretical model that they teach in CS programs.

Some teach this but many don't. They spend their time climbing the hierarchy and saying the word "exponential" again and again. The classes are obsessed with seeing every problem in Gary and Johnson as intractable.

My point is that many of these theoretical models cause as much trouble as they solve.

Re: The case against CS master's degrees

#25

Earlier quoted context omitted.

I don't know if anyone (anymore) thinks that computer science is the same as software development. Knowing the latest library APIs, versus doing research to find a faster hash sort, are two different areas, IMO. I also wonder about the different industries and how they compare (SaaS vs CGI vs HFT). I think if you want to forge new roads in programming, a little theoretical studying doesn't hurt, so why not explore a…

So why not explore a university degree? Let me give you 300,000 reasons-- in other words, the price (in dollars) at a fancy university for said degree. I'm not debating whether anyone should study this. I'm just saying that people who want to get jobs shouldn't need to study it. If you want to do the theoretical stuff, have at it. I'm just saying that it's failed my team as often as it has helped. If the theoretical…

Do you think that this is only true of CS and programming, or of any degree and any job? And if not, what makes CS and programming special?

Re: The case against CS master's degrees

#26
post #5
post #4

I hate to be super-negative, but I'm not even sure a bachelors in CS is a good idea. Oh sure, you learn a few good things along the way, but then the professors start dragging you down their favorite theoretical paths. I'm all for philosophizing and navel gazing, but there's not much practical in things like lambda calculus, NP-completeness and some of the other topics. To make matters worse, these pursuits can confu…

In my experience, the biggest reason doing a bachelors in CS sucks is because it's a massive waste of time, leaving little to no time for side projects. Programming assignment questions tend to be vague and come with poorly scoped requirements. Usually the professor also forgets to tell you several essential details or has made several errors in the code. An average assignment can take upwards of 40 hours, with 10 or…

Luckily, not all universities are that crap.

Re: The case against CS master's degrees

#27
post #12

Earlier quoted context omitted.

I'm only being partially snarky when I say that sounds like a great preparation for working in a production environment.

Every time I make this point someone says something to this effect. If you spend your career writing garbage for a ransomware gang or an outsourced app development agency you probably won't have too high an opinion about software development. It's just a difficult thing for me to believe that this happens in large amounts at the best companies.

Most jobs aren't at either of those two extremes (garbage vs best companies). There's a lot of work in the middle, where your job is to use your tools to facilitate a business outcome; if your boss has to tell you how to do it, the company probably hired the wrong person.

Re: The case against CS master's degrees

#28
post #5

Earlier quoted context omitted.

In my experience, the biggest reason doing a bachelors in CS sucks is because it's a massive waste of time, leaving little to no time for side projects. Programming assignment questions tend to be vague and come with poorly scoped requirements. Usually the professor also forgets to tell you several essential details or has made several errors in the code. An average assignment can take upwards of 40 hours, with 10 or…

At U of Washington you get to choose your own senior project (so I've heard firsthand).

Wait, that's not the norm? What's the alternative, do they just let a professor invent a couple dozen projects?

Re: The case against CS master's degrees

#29
post #4

I hate to be super-negative, but I'm not even sure a bachelors in CS is a good idea. Oh sure, you learn a few good things along the way, but then the professors start dragging you down their favorite theoretical paths. I'm all for philosophizing and navel gazing, but there's not much practical in things like lambda calculus, NP-completeness and some of the other topics. To make matters worse, these pursuits can confu…

Part of the value of a CS degree is that many students incidentally end up RTFMs for a lot of stuff before they start their first job. Which makes them slightly less useless in their first few years.
Post reply on HN