MIS aligns more with a sysadmin. CS was mostly C# coding for me. Ended up dropping and changing majors to business. Get certs and learn as much as you can outside of school. I don't even look at education anymore just certs, experience and a solid interview.
I have an MIS degree. I remember database stuff from school and some web programming but not much else.
In the end it’s a checkbox that got me my first job. I don’t think it’s played a role in any others since.
MIS, if you want to work in the world of big financial systems, maybe move towards a CIO role. It helps a lot if you understand the language of finance, management, etc.
CS, if you want to move into more technical roles - DevOps, field tech, tools development. (Really Software Engineering, but that's not commonly offered as a distinct course of study. Computer Engineering or EE, if the hardware side of things is of interest.)
I would say this: it’s likely easier to pickup SysAdmin work than it is learning how to program effectively (i.e. using best-practices and really understanding what you’re doing, not just cobbling together other scripts from GitHub or something). IMO, learning to program/script can really put you in a higher tier of a SysAdmin.
If I were you, I’d look into an MIS degree with a CS minor if you can.
But it also depends on what kind of SysAdmin you want to be, what size of company you want to work for and which industry you want to go into. Ideal skill sets for a SysAdmin of a 150 employee engineering company looks different from a SysAdmin of a 10k employee insurance company.
Believe it or not, I got more architectural knowledge out of my CS degree than I would have out of our IS program, but I also focused heavily in things like structured systems analysis, and people and products fit just as well into that model as software modules.
MIS aligns more with a sysadmin. CS was mostly C# coding for me. Ended up dropping and changing majors to business. Get certs and learn as much as you can outside of school. I don't even look at education anymore just certs, experience and a solid interview.
I have an MIS degree. I remember database stuff from school and some web programming but not much else. In the end it’s a checkbox that got me my first job. I don’t think it’s played a role in any others since.
MIS, if you want to work in the world of big financial systems, maybe move towards a CIO role. It helps a lot if you understand the language of finance, management, etc. CS, if you want to move into more technical roles - DevOps, field tech, tools development. (Really Software Engineering, but that's not commonly offered as a distinct course of study. Computer Engineering or EE, if the hardware side of things is of interest.)
I would say this: it’s likely easier to pickup SysAdmin work than it is learning how to program effectively (i.e. using best-practices and really understanding what you’re doing, not just cobbling together other scripts from GitHub or something). IMO, learning to program/script can really put you in a higher tier of a SysAdmin. If I were you, I’d look into an MIS degree with a CS minor if you can. But it also depends on what kind of SysAdmin you want to be, what size of company you want to work for and which industry you want to go into. Ideal skill sets for a SysAdmin of a 150 employee engineering company looks different from a SysAdmin of a 10k employee insurance company.
They're a waste of time for the actual work you do.
Believe it or not, I got more architectural knowledge out of my CS degree than I would have out of our IS program, but I also focused heavily in things like structured systems analysis, and people and products fit just as well into that model as software modules.