Originally posted by: LordJezo
...there really are no CS jobs out there so it really dosnt matter.
Originally posted by: NTB
I'll go along with jzero on this one. I actually tried CIS for a semester before getting into Computer Science instead. I wanted to work with computers, but I wanted to do more than just make the occasional website, learn how to use Office and maybe a few other programs and do some tech support - which is basically what the C in CIS was turning out to be. The rest was all buisness. So next semester I signed up for a few programming classes and haven't looked back since 😀.
Originally posted by: dcpsoguy
Seton Hall does not have computer science or programming, but it does have Computer and Information Sciences. Would I be able to get a game programming job with this major?
Originally posted by: jaeger66
If I had to do it over again I'd go with CIS instead of CS. It's a lot more practical. If you want to be a serious programmer and go the CS route, you'd better be good at it and you'd better love it. Otherwise you're just going to be fighting over the scraps.
Originally posted by: Jzero
What would you do with a CIS, though?
Seton Hall does not have computer science or programming, but it does have Computer and Information Sciences. Would I be able to get a game programming job with this major?
Seton Hall does not have computer science or programming, but it does have Computer and Information Sciences. Would I be able to get a game programming job with this major?
I honestly don't know any MIS/CIS people that would be any good at Systems Analyst or DBA. The guys with Masters degrees in MIS at my office didn't even know how to install SQL Enterprise Manager, let alone operate it. I'd like to say that it's because their background was in Unix and they simply weren't exposed to Win2k and MS SQL, but....they don't know seem to know anything about Unix and non-MS dbs either....Originally posted by: jaeger66
Originally posted by: Jzero
What would you do with a CIS, though?
Probably the big 3 would be systems analyst, DA, or DBA.
They definitely didn't take any 400 level programming courses. They took VB. They took a software engineering course where they learned how to "design" software, but not how to program. Maybe your school has it wiser. At Drexel and TCNJ, I stand by my opinion that MIS/CIS is just an attempt to make the school of business look "with-it"You're not going to be a hardcore code guru, but you should still have plenty of 400 level programming courses.
I dunno. I didn't take any physics, and I only had to take up to Calc II, Linear Algebra and Stat. There wasn't a big focus on math, and we had the same science requirements (2 semesters of gen. physics/chem/bio and 1 of geology/astronomy) as the business school. The difference seemed to be that while the CS majors got a full-scale programming education and the Management and other biz majors got a full-scale biz education, the MIS people just got a half-assed attempt at combining the two.The main difference between CIS and CS is that the math and physics are replaced with business and management courses, and the programming courses tend to ignore the theoretical stuff. These days, business, communincation, and leadership skills are more useful than 5 levels of calculus. Unless your total focus and career goal is programming, that is.
Originally posted by: Jzero
I dunno. I didn't take any physics, and I only had to take up to Calc II, Linear Algebra and Stat. There wasn't a big focus on math, and we had the same science requirements (2 semesters of gen. physics/chem/bio and 1 of geology/astronomy) as the business school. The difference seemed to be that while the CS majors got a full-scale programming education and the Management and other biz majors got a full-scale biz education, the MIS people just got a half-assed attempt at combining the two.
Just my impressions. The problem with CS is that it's still taught by smarmy ex-mathematicians who think that there is nothing else to computer science except for math and programming. They do this at the expense of teaching about networking, administration, security, and other less programming-intensive aspects. It's frustrating...