In the industry, this is a concept that has already been talked about quite a bit. In fact, a common mantra heard at AMIA conventions is the oft recited, "Any physician who can be replaced by a computer should be."
Unfortunately, that is MUCH easier said than done. And while clinical decision support systems exist to help physicians with their patient diagnosis, every physician uses them as a guideline, and not as an absolute reference or comprehensive source of information. Experience is heavily valued, which is why every physician has 7+ years of postgraduate education and working in the field.
You are considering the wrong criteria in getting a degree. You should instead be asking yourself, "What would I enjoy doing more?" The passion in doing what you enjoy is the best way to maximize your earning potential. You will enjoy going to work everyday, you will be excited to take on and complete diverse projects, and your passion and drive will be obvious to anyone who is around you. People will interpret this as a hardworking ethic at the company , and/or love of the company you work at which will in turn translate in to a higher income.
So if you are interested in setting policy, go for your MBA. If you are interested in applying computer technology to the business setting, go for the MS in IT degree. If you are interested in programming, and the creation of computer tools, go for the MS in computer science. However, there are many fields of study that you did not mention that may be of interest as well, everything from software engineering (specialization in writing software), to computer engineering (designing specialized computing devices), to HCI (how people interact with computers), to the numerous sub specialties of informatics (I'm personally studying health informatics, and the creation of unique tools to better health care and help clinicians be safer and more effective).
Sounds like you need to do more research into what you want to do for the rest of your life, and change the criteria basis for which you are basing this decision.
Exactly, make the hint button inaccessible for several seconds after a move has been made, justifying it by saying they haven't tried long enough to try figure out the next move. Imagine if you were sitting next to the player, what kinds of hints would you give them, and how often?
Developers should respond to the requests of their users, however, those requests should be tempered be the social aspect of user (player) interaction with the software (game).
What is now proved was once only imagin'd. -- William Blake