computer college !

Is anyone in/went to college for a computer degree?

Please give us all insight about the process and where it got you and what you found to be the most essential knowledge while going for the degree?

Step 1:  Research.

What's a "Computer Degree"?  Computer Science?  Engineering?  IT?  Go figure out what it is you're talking about, then come back and try again.

I did computer science, it got me absolutely nowhere since all the programming/IT shops require 3+ years commercial experience in all the latest management buzzwords. Unless you do really well then you can get hired by a big company such as IBM where you will be trained on the job, which in otherwords means you get to be a codemonkey and learn to hate programming.

>>3 speaks truth.

Do yourself a favour: if you're not doing at least co-op stream in CS, don't even bother.

>>3
so.. How the fuck do you penetrate the industry, then? Isn't there at least demand for small-time jobs?

Whatever happened to going to college and doing what you were taught to do? :( I miss the 60s.

"How the fuck do you penetrate the industry, then?"

VERY GOOD QUESTION.

All you have to do is get lucky. That's how I started in IT.

>>5
>>6
>>7
Truth, it's the same here in Europe.

DO NOT GO TO DIGIPEN.  Get an actual degree at a four year college without it being a complete waste of your time and money.

>>5
Get very fucken lucky las >>7 said.

>>1
Assuming you mean CS degree, ask yourself if you have the drive/desire to be either a researcher or a programmer ten years down the road.  If you really can't see yourself as either, reconsider.  If you have soome interests in programming and know you wouldn't mind being a manager, get a MIS.

>>10

Just what I need to deal with, another clueless manager who thinks programming is that VB class they took their 3rd year of college.

>>3 speaks the truth only for those who enter programming for money.  If you go into software dev't because you love software dev't, you can get a job quite easily (as long as you're willing to relocate). 

I graduated with a 4 year degree in Computer Science and Engineering, dropped out of grad school after a coupla' years due to "out-of-money" syndrome, and got my entry-level job at well above the industry average salary for a recent grad

Of course, I like software dev't.  I read technical books recreationally.  If you aren't driven to the point of learning it on your own, save the world from another clueless codemonkey whose shiatty software I'll have to fix and go get an education degree instead.

>>10
I'm not sure what university you went to but doing the MIS program here left you only a few courses away from a CS major.  We had no VB courses either.

err the >>10 in >>12 should be addressed to >>11..

>>12 & >>13

This gets to the root of a lot of problems I have with MIS and straight CS degrees.  The quality is widely varying.  I've seen CS degrees that'd smack my CS&E degree around like a little bitch.  Likewise, I've seen CS degrees that are little more than "Microsoft Software for Morons".  I've seen similar variance in MIS degrees.  (My own school's MMIS degree was less than exemplary.  I was tutoring one student for a semester in the second half of his third year when he took "UNIX and C".  He was a nice guy, but he couldn't get the idea that a programming language and an operating system are two different things.  He thought that C == UNIX.  "But, I know how to program!  I made a clock in VB!"  Riiiiight...)

I would never, in a million years, want someone so technically inept as to be at that level of understanding after *three years* to manage software development.  IT & Desktop support, maybe.  Software dev't, never.

>>14
Fair enough.  I was just trying to tell >>1 that even if you do programin your own time, get the satisification and all that from it, a straight-up CS degree and the eventual software developer job might not be what you want.  That he shouldn't think, oh, I enjoy programming as a hobby, maybe I can do it for a living.

He thought that C == UNIX.
UNIX was made in C and C was made for UNIX. They practically are the same thing.

>>16

Thank you.  You're an idiot.  You may shut up now, or continue talking and providing entertainment for anyone who has half a clue.

>>17
U

UNIX was originally written in assembly.

>>18

Internet, much?

>>16

C is a programming language.  *nix is an operating system.  Claiming that they're practically the same thing is like claiming that potatoes and imaginary numbers are practically the same thing.  They're completely disparate entities.

Windows is Visual Basic!

>>21
Well, they are both shit.

Windows written in Assembly, C, and C++, like Linux.

>>22
gb2/tree in a house you goddamn hippy. Visual Basic sucks, but there are many features Windows has, besides workstation performance, Linux can't dream of yet.

>>23
Lol, make that house in a tree

>>20
It would be more like claiming that potatos and starch are the same thing.

Here's another claim for you to get all aspie about: the history of the internet == the history of Unix.

>>25
That's why HTTP, Internet's most used application protocol, uses CR-LF to separate headers, right?

HTTP is a newer protocol. RFC1945 only was from 1996, after trumpet winsock and then Win95 came along.

It's supposed to be readable, and Unix linefeeds don't work that well when viewed by windows.

>>27
Lies, 4 out of 5 editors/viewers I use work with them. Notepad.exe is prolly the only one that fails it.