CS will lay the ground work to create and understand any IT technology.
I've been in the field for awhile (since the early 90's) and I concur. After exiting the military as an electronics tech, I decided to work on an IT major. That was a mistake. As somebody who hacked Vics, Cocos (OS-9 Baby!), and Atari800s back in the day I started looking at all the CASE and RAD crap they had us doing with absolutely no understanding as to what was going on behind the scenes. After three years (and an easy 3.9 GPA) I dropped out of that program, and I've been tooling away on a CS degree since then (nothing like being a university senior in your late 30s..heheh).
Even if you're an applied guy like me (I admin UNIX and do a bit of application development), actually writing part of a protocol stack or tearing a part a database engine is worth its weight in gold. A course in programming languages can make you look at learning a new language in a different (and more efficient) way. And as others have said, the mathematical underpinnings still apply.
The Achilles' heel for a lot of CS folks is the lack of a business background (which MIS guys will try to flaunt). Get an MBA if that's your gig and dominate them.
Slashdot Mirror
Even if you're an applied guy like me (I admin UNIX and do a bit of application development), actually writing part of a protocol stack or tearing a part a database engine is worth its weight in gold. A course in programming languages can make you look at learning a new language in a different (and more efficient) way. And as others have said, the mathematical underpinnings still apply.
The Achilles' heel for a lot of CS folks is the lack of a business background (which MIS guys will try to flaunt). Get an MBA if that's your gig and dominate them.