Well, I thought the discussion
here, was on that topic.
A few random points...
I was a physics major myself (I double majored). I think physics is a great background for many fields, EE/CS, science, engineering, financial, economics, consulting, medicine, etc. Physics is very good at building general analytical skills.
MIT's Associate Dean for the School of Engineering recently felt too many MIT students ended up in cubicles. That is to say, doing engineering work, but never moving into engineering management, or into other fields such as politics, social services, etc, fields which generally require more people skills. To compensate for this, MIT began a new program
UPOP. I stand behind, and agree with the goals and princples of the program 100%. Convienently, my friend is the director of the program, and I actively participate in it's development and execution.
This whole question is really the basis of my book. Fundamentally, my answer is, "no it doesn't, here are some additional ideas
you should keep in mind when working in software." It's aimed at people in software with 0-5 years experience, designed specifically to fill in the gaps left by a CD program. So, in fact, I could spend quite a lot of time talking about this topic--for about 170 pages so far. I'm hesitant to go into further detail just because I should really be focusing my energies on this topic into the book to get it done (I've slacked off a bit lately and need to gear up again). Nevertheless, you can be sure that I will post much more detailed answers to these and other questions when my book get close to publication.
--Mark
[ July 17, 2002: Message edited by: Mark Herschberg ]