Slashdot Mirror
Learning About Outsourcing in College?
nial-in-a-box asks: "I just started my software engineering course today at Loyola University Chicago and I found out that I will be learning hands-on about outsourcing. My classmates and I will be outsourcing parts of projects to students at another university, and then those students will be doing the same for us. This seems like it could be rather interesting. Has anyone out there been in a class like this before? Any other ideas on how to effectively teach about the implications of outsourcing (especially pointing out that outsourcing doesn't necessarily mean no jobs upon graduation)?"
...a lot of documentation... *yawn*
they could outsource the entire class (except for "upper management", i.e. the prof). the students would have a few weeks to prep foreigners on what they would do in various situations, and then the professor could teach the foreigners via conference calls while the students go look for other classes.
Propose to get another person to take the classes for you. When they say you can't do that, you tell them you're outsourcing.
Then ask them what the differenc is, really. This might turn out into an econ/ethics class, so make sure you got your econ 160 stuff down pat.
"Piter, too, is dead."
This is part of the new curriculum being phased in at CS programs around the country. The next phase will have you deposit your diploma into a shredder for recycling after you cross the stage. You'll then be loaded onto a container ship and be sent to a reprocessing facility in China, where you'll become something useful, like soylent green.
-Isaac
I am not a lawyer, and this is not legal advice. For Entertainment Purposes Only.
Regarding question 1; Yes, the University of Toronto Computer Science classes have been doing this for years, but mainly between groups within the same class or classes.
:)
Question 2; I hate to point out the obvious, but they are not teaching you about "outsourcing"; they are really just using that as a term to describe what you will be doing. They are attempting to teach you how to work with others effectively when face-to-face communication is not always possible. In programming, this means properly internally and externally documenting code, and defining clear interfaces. Since this is a situation will come across very often in the working world, it is important to learn. Also, in this class you are not only held accountable to your professor, but also to the students in the other school.
I believe it is an excellent way to teach important lessons to students. When you have an interview with a company, I would suggest pointing out this class to the interviewers and telling them what you learned from it; it'll probably impress them. Have fun!
[o]_O
Because they're not trying to teach the lesson of what it's like to lose your job. They're not trying to teach you to be a smart-ass.
I would think there is a very practical lesson to be learned in telling someone at a remote site exactly what you expect to see, and exactly what it's interface will be, and how you plan on verifying it. This is a practical exercise in writing your spec in advance and handing it off to someone to implement. Which, oddly enough, is arguably applicable to software engineering.
An awful lot of projects never really know what they're looking for until they get a few iterations in. I'm willing to bet if you did that in an outsourcing project it would become extremely inefficient.
I'm betting the prof is counting on several bad specifications going out the door which are either completely useless or way too open-ended. In which case the people who implement it will deliver what they understood the requirements to be -- the coders will be judged by how well they implemented what was asked for, not what was wanted by management.
Cheers
Lost at C:>. Found at C.
To make it even more realistic, they should get a bunch of clueless business administration students to come in and grade your work.
It's good to use your head, but not as a battering ram.
Just something I wanted to toss out here...
Really, if these jobs are going to Indians with CS degrees...why wouldn't they deserve the job? If they're qualified, why not give them work? I mean, if two workers are both qualified, and one will work cheaper, you hire the cheaper one.
And if you think they're not qualified, then one of two things would happen: either companies will see the difference in quality, decide it's not worth the cost savings, and start bringing the jobs back...or they'll decide the quality is good enough, that it offers a better value for their money, and there'll start to be a lot less high pay programming jobs in the US. Companies may just not need as highly skilled programmers as they thought. To them, it'd be like hiring an engineer to be a janitor, when he was still demanding an engineer's salary. Either he's gotta drop his price, or the job's going to someone else.
I guess people just need to realize that programming, as it's done by most large software companies, isn't really skilled work. It requires a lot of training, yes, but so does being an auto mechanic. Sure, there'll always be smaller companies that have a need for highly skilled programmers. Id isn't going to start outsourcing. But a young, technically-minded individual will just have to consider other career paths than programming. Low-level programming jobs aren't going to disappear in the US, but they'll prolly pay a lot less and just generally be a lot less glamorous.
hot foreign sheep.