Slashdot Mirror
Microsoft Invests in the University of Waterloo
saforrest writes "Say goodbye to independent academia. In a presentation by Microsoft on Wednesday at the University of Waterloo, a new joint initiative was announced which involves the addition of a mandatory course on C# for all electrical and computer engineers. 'Completion of this course
will be mandatory for students entering the E&CE
program.'" Microsoft's press release is available.
*sigh* I had hoped that the mathematics & Comp Sci department at U of W knew better. But who am I kidding? When I went there, we used to joke about how U of W's secondary campus was located in Redmond - given the large # of UW CompSci co-ops and graduates that worked there.
Ah well, at least my old Physics department is underfunded (wait... RIM is investing $150 million in a new Physics research institute @ the U of Waterloo? DOH!)
Waterloo always had close ties with industry. Now they appear to have an umbilical cord.
The fact that this University is willing to sacrifice any sort of appearence of propriety in order to squeeze a few bucks out of Microsoft is as pathetic and outragous as if they were to let the parents of poorly-performing students buy their way in with large cash donations.
Of course, the latter example happens all the time, but at least they don't brag about it in press releases.
Anyhow, it seems to me a horrible idea to set this sort of prescident. What's next? Coke gives a few bucks to the football team and suddenly all students have to undergo a session about the crisp, refreshing taste of Coke, Diet Coke and Sprite? The music industry buys the U a building and, next thing you know, all students are required to buy $300 of Britney and N'Sync albums for their music appreciation courses?
Universities should be about education, not indoctrination. Unless these are the best languages for teaching the foundations of computer programming (and they are not), they shouldn't be required.
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
First they came for UW, and I didn't speak up because I didn't go there...
It's a good deal for both sides.
Deals between hospitals and insurance companies for managed health care are good for both sides. But are they good for the patient? Deals between the military and arms contractors are good for both sides. But are they good for soldiers & taxpayers? Hypothetical deals between congressmen and lobbyists ("hypothetical" because there is, of course, no quid pro quo) are good for both sides, but are they good for voters and citizens?
Is this deal good for the students of UW? THAT is the only question that matters.
There is a reason why serious academic institutions do not overwhelmingly adapt Microsoft. Primarily it is the cost both in dollars and also in loss of academic freedom that comes with the restrictive licensing that comes with many proprietary applications. One of the founding tennants of higher education is that information should be freely and intensely pursued. Sure some "MIS" programs may just be an advanced MCSE/CCNA course, but most real computer science programs could not afford such a narrow scope. CS by definition is much more broad than software developement, MIS, EE, or networking; rather it is the culmination of all of the above with other studies mixed in.
Any CS program that concentrates too heavily on one thing (ie programming in C# or Java for that matter) really short changes its students and limits the potential that they can achieve. A much more broad approach, while not churning out top notch Java developers, produces excellent problem solvers who are able to quickly learn and adapt to the ever-changing technology world. Looking back on my undergrad experience I think that playing around on the HP-UX and AT&T UNIX (R) box helped me break out of the mold and learn much more effectively.
If the CS department is worth a 1/2 a crap it doesn't really matter what language[s] they teach the classes in. The students should come away with a good solid foundation of general programming knowledge. Languages come and go, if a CS grad needs to know one they should be able to buy the reference and compare to their base of knowledge. Note: I'm not saying CS grads should be guru's in whatever language they choose after a day, but they should be able to get by.
They who would give up an essential liberty for temporary security, deserve neither liberty nor security
Beyond the fact that C# isn't by any stretch the best language to teach concerning the basics of computer programming (and as such is a disservice to the students at large), this also sets a horrible prescident. Maybe Putnam can buy this U a new administrative building and get a new mandatory lit class added -- "Lit 203 -- The Works of Tom Clancy"
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
What is not acceptable, however, is for grants from a company to be tied to the use of its products in the curriculum. And, in fact, while C# is fine technically and educationally, Java would still be a more useful language for students to learn.
Decisions like this really call into question the academic integrity of a university; potential students of U. of Waterloo should take notice.
(Disclaimer: I'm a former Waterloo CS student. Left for my career without graduating around the beginning the dot-com bubble, still employed, no regrets.)
.NET rarely considered elegance an important facet of keeping software costs low. The only grads that have design skills and/or good business skills usually are self-taught.
I agree with your assessment that there's a mythos behind UW students that seems to be carried among other companies as well, particularily in professional service firms, whether smaller ones or larger (like Accenture). But this mythos isn't entirely without basis.
I would generalize your observation to include my own experiences interviewing and working with UW co-ops and graduates: many UW students often *do* interview better than most other graduates and/or interns. And they often do generate better-than-average results. Over the past 2 companies I've worked for on the U.S. west coast and the east coast -- management fell in love with UW students.
I would attribute this to what some might find surprising: many CS and Eng students at UW have very good communication skills relative to their peers in other schools. The co-op program requires them to be good, since they have to work in between heads-down course work. Naturally every class has legendary high-mark/anti-social students, but they wind up being professors anyway *grin*.
A secondary reason for UW student's success at Microsoft and PSFs is that UW tends to hammer programming skills into CS students, even if it kills them (as anyone who's taken Operating Systems will attest to).
Being relatively professional speakers, the best UW co-ops are usually both confident & technically savvy enough to be placed on the front-lines to do real work -- whether in front of a client for a contract, or @ Microsoft with the culture of debating ideas.
Usually the UW co-ops and/or graduates I have known have been better than many full-time employees at client sites. But not perfect. I find UW grads, like all grads, have a lot of learning to do in placing systems work in business context. There's also a general lack of both high and low-level design skills, and an overemphasis on tricky algorithms and/or cleverness. The cynic in me believes this makes them fit right into Microsoft, which until
So, in summary: there is a myth around waterloo students, but not entirely unwarrented. They're more experienced programmers than most regular interns from other schools, and often they can be better communicators.
-Stu