There's a program in my university called "Management Information Systems." I suppose I should look at what kind of things their majors do, and what their jobs are usually like?
MIS more prepares you for building IT in regular business. It's broad but shallow; you learn about database design, project management, application development, networking, the whole gamut (depending on your school). You learn the real stuff on "the street" anyway. Companies typically treat it as equivalent to a CS degree. You can get into whatever industry that interests you.
*I switched from CS to MIS and glad I did, but this info is 20+ years old, things might have changed since.
The minor in business can take you in some of the management positions in IT, experience can take you into others. But the minor in business can also take you out of IT.
Nothing speaks against finding a job you “like” (love is asking much of a job) and turn tech into a hobby and going more into electronics instead of software. To be honest technology makes a nice and exiting hobby but often a less exiting Job. As soon as a cool idea meats up with customers things can get ugly for stupid reasons.
I'm saying this wery lightheartedly - I felt like 80% of the people in MIS programs where people who needed (because society dictates you have to get a degree) to go to college and didn't care really care about tech or business, but they need a degree so why not both? 10% were people who should have majored in CS or Business, but for some reason didn't realize it early enough in their college journey and they didn't want to redo 1-2 years of coursework. The other 10% were destined to become the a$$hole VPs/SVPs who everybody hates, and the MIS degree was just another step to world domination and them self-justifying that they have a "technical" background.
>Companies typically treat it as equivalent to a CS degree.
I don't think this is true at all unless the company is one of those who hires SWEs who don't really do any actual software engineering.
I really enjoyed it though. I learned so much that my first job utilized everything I learned. At a small growing company that needed in-house expertise. I did the network, the switches, the workstation builds, the servers, built the database and applications on top of it all. I did project cost/time estimates and carried them out. After about a year we hired a full time network/client guy and I stuck to applications / database. It was a lot of work but I really enjoyed it and got a lot out of it. I don't think I would have been able to cover that much ground with just a CS degree.
>I don't think this is true at all unless the company is one of those who hires SWEs who don't really do any actual software engineering.
I don't know if it's still true, but when jobs would require "CS degree or equivalent," they meant MIS/CIS, at least 20+ years ago.
You are most certainly an exception to most people I knew in the MIS program at my school. :)
>I don't know if it's still true, but when jobs would require "CS degree or equivalent," they meant MIS/CIS, at least 20+ years ago.
I'm old enough to remember when people I know would graduate with "MIS" or "IT" degrees and get a $55K job building and installing Windows NT 4.0 servers with a bunch of other stuff (e.g. networking) on the side. It was a great starting salary at the time. Then the dot-com bust happened.
I definitely think software engineering now is at the point where CS or STEM degree really means that. Programming has just become a lot more specialized than back then. Well, at least hiring managers seem to think so...
The end result is that there is a wide variance in what people do after they graduate, and the degree isn't really an indicator of anything other than them getting a degree.
I have one of these generic multi-disciplinary undergraduate degrees and honestly, years later I feel like I would have less regret about how I spent those 4 years had I done CS or another program that was more focused. YMMV.