[tomjen3]

No you won't. Academia thought me how to be a better programmer, about compiler construction, functional programming the theory behind OO programming, prolog, how databases actually work (IE not just some random subset of the sql language) how 3D graphics work (including how to compute light and how you go from a mesh of triangles to an image on a screen), Haskell, SVN and how to work on large projects with others (including many of the issues that are not just technical, etc). While there were a few classes that was a waste of time (how to design enterprise systems and usability comes to mind, since the first is just a matter of ticking of enough boxes and the second is do what the user expect) most of them wasn't.

There is a real bias against CS degrees in certain circles, which I suspect is fueled in part by a couple of bad experiences with no-good hires (which exist in all professions) and in part by a feeling of inadequacy some who never got a degree might feel.

[nupark2]

As a hiring manager, my 'bias' against CS degrees, such as it exists, is that they don't actually tell me much of anything.

Individuals have the capability to learn "compiler construction, functional programming the theory behind OO programming, prolog, how databases actually work", et al, independently of a degree, and yet, having that degree doesn't seem to actually guarantee that a potential hire understands any of the above.

[shaggyfrog]

Then you shouldn't have a bias against CS degrees; you should simply see them as zero-information attributes.

(Which, I think, is correct in a general sense: a resume should get a candidate to an interview, not earn the job on its own.)