There are, roughly, two types of programmers. One type was in the computer club at high school and got a computer science degree (or two or three). The other type, well, didn't--they were English majors, college dropouts, busboys, artists, odd-job-doers. (Cue Captain Renault: "That makes Rick a citizen of the world.")
My advice to young people is to get a computer science degree, if for no other reason than you can avoid those odd jobs and get right to the programming. And it also gives you an early chance to find out if you were, in fact, born a programmer.
In my experience, in general, I prefer working with individual programmers who didn't get a CS degrees. That's not universally true: there are some CS-degree holders I love to work with. And it doesn't imply a particular causal relationship: it could be that people I enjoy working with are simply those who are less likely to get a CS degree, rather than my enjoyment stemming from the fact that they didn't.
Reverse order for me... (Score:1)
Agreed (Score:1)
Re: (Score:1)
I started teaching myself when I was a young teenager, and all I've wanted to do since then is program. For a while I seriously thought about going into other fields (strangely, physics was one of them), but I drank the cool-aid and chose CS. I learned a huge amount of practical prog
Re: (Score:1)
Anyways, here [stanford.edu] is a sample undergrad curriculum. I'd say about half of it could be skipped without significant loss in programming ability: about half of the math requirements (e.g. calculus), the physics, almost all the hardware/EE, and some of the ran
10 types?? (Score:1)