It's back to school for IT
I thought you all might be interested in this article and the thought provoking comments made by some readers at the end.
It seems like all Mr. Blake is saying is that CS is an outdated degree, and that IS (Info. Systems) would be a better choice, although he doesn't realize that is what he is saying. Instead, he attempts to validate CS as directly viable to business development, if only we could change it....
In CS, all students are learning is coding and theory, whereas in IS you get a full blown business degree, and a healthy dose of programming and systems knowledge as well. How can you even start to know how to integrate a system when you don't know how a business works?
This is where CS is a failure. It is a specialized, technical degree, and IS's job is to use these CS people to create systems that work together for the good of the business. IMO there is no use trying to morph a CS degree into a more "business friendly" degree, because such a degree already exists!
CS = code junkie
IS = use code from code junkie to work into buis. goals
If you start to blend these two degrees you will lose the specialization each one offers. One person cannot write the code and figure out how to integrate it into the highly complex business structure in the best way possible.
It's like having the accountant ordering servers... sure he knows what fits into the budget, but he has no idea what the needs of the company are concerning server hardware.
Well I'm sure I have stirred up quite a hatred for myself, so I will end now.
Those of you who might be more experienced on this issue, please enlighten me on your perspectives. Your comments will be taken with an extremely large grain of salt.
*puts on flame suit*
So...
Can/should CS by melded into IS to form a single business friendly unit?
Or do they need to be kept separate so each can specialize in his/her own area?
I thought you all might be interested in this article and the thought provoking comments made by some readers at the end.
It seems like all Mr. Blake is saying is that CS is an outdated degree, and that IS (Info. Systems) would be a better choice, although he doesn't realize that is what he is saying. Instead, he attempts to validate CS as directly viable to business development, if only we could change it....
In CS, all students are learning is coding and theory, whereas in IS you get a full blown business degree, and a healthy dose of programming and systems knowledge as well. How can you even start to know how to integrate a system when you don't know how a business works?
This is where CS is a failure. It is a specialized, technical degree, and IS's job is to use these CS people to create systems that work together for the good of the business. IMO there is no use trying to morph a CS degree into a more "business friendly" degree, because such a degree already exists!
CS = code junkie
IS = use code from code junkie to work into buis. goals
If you start to blend these two degrees you will lose the specialization each one offers. One person cannot write the code and figure out how to integrate it into the highly complex business structure in the best way possible.
It's like having the accountant ordering servers... sure he knows what fits into the budget, but he has no idea what the needs of the company are concerning server hardware.
Well I'm sure I have stirred up quite a hatred for myself, so I will end now.
Those of you who might be more experienced on this issue, please enlighten me on your perspectives. Your comments will be taken with an extremely large grain of salt.
*puts on flame suit*
So...
Can/should CS by melded into IS to form a single business friendly unit?
Or do they need to be kept separate so each can specialize in his/her own area?
