<p>
</p>
<p>You’d think so, right? But not really. In fact, not at all. For several reasons.</p>
<h1>1 - You have to be familiar with the particular development environment that the firm is using. Just to take one, let’s say that the prospective employer is using Ruby on Rails. Now, you can be the greatest algorithm coder in C in the world, but if you’ve never actually used RoR, you’re probably not going to be hired. Now, granted, it probably wouldn’t take you much time to * learn * RoR. But employers don’t really care about that. Whether we like it or not, CS employers want to hire people who can hit the ground running. This is incidentally why a lot of otherwise good CS grads don’t get hired, because the specific skills they learned in school are often times not the most useful and practical ones.</h1>
<h1>2 - Design is a skill unto itself. Just because you’re a great technical engineer doesn’t mean that you know how to design well. Look at the history of Apple. Was the Macintosh the technically best computer in the world? Of course not - IBM had been building mainframes for decades before that. What made Mac successful was that it was * well designed . Apple didn’t have the most technically savvy computer engineers in the world (as most of them were probably working at IBM). What Apple had were engineers who knew how to * design well. Similarly with the Ipod - the Ipod was not the most technically advanced MP3 player in the world, nor was it the first. MP3 players had existed for years before the Ipod came out. What the Ipod offered was top-notch design. The Ipod defeated all of the other MP3 players because it was designed to look cool and was designed to be easy to use in the way that the other players were not.</h1>
<p>Speaking to the specific example, good algorithm design basically requires deep mathematical insight and savvy. But good design work requires an intuitive understanding of what customers will like. Those are 2 entirely different skills. Other companies, like Apple, seem to have a knack of figuring out what customers really want. Other companies (i.e. all of the other MP3 player manufacturers) do not have this knack. </p>
<p>
</p>
<p>No doubt, and I never said that it did. But that’s not the point. Sure, if you can have both, it’s great to have both. But at the end of the day, as a student, you care about a school that is going to help you get the job that you actually want to get. Most engineering students have no intention of becoming researchers. </p>
<p>
</p>
<p>Exactly. So you agree with me that what really matters to you as a student is getting the job that you want. Hence, you cannot conclude that just because Yale may not offer extensive engineering research opportunities, that it is not a good school. If the Yale engineering students are getting the jobs they want, then that should be the end of the story. </p>
<p>
</p>
<p>Nobody has ever argued that there are some MIT profs who do care about teaching. Of course there are. But the point is, many other MIT profs do not care, and just want to spend their time on research. If you’re fighting for tenure, such an attitude is perfectly understandable (albeit sad), because research will get you tenure, but good teaching will not. </p>
<p>
</p>
<p>Well, I don’t know, are you? It seems that you are judging an education based on whether it can get you a job. Well, if that is your metric, I highly doubt that Yalies are complaining. </p>
<p>
</p>
<p>What I am saying is, if the employer has the choice, why would an employer take the chance of hiring somebody who comes from a school that is known to be mediocre, if you can hire somebody else? </p>
<p>Surely you know how the world works - that one bad apple can ruin the perception of the entire bunch. For example, let’s say that a new manager hires somebody from school X, and that guy turns out to be bad. You know what’s going to happen - that manager is not going to want to hire anybody from that school again. Not only that, but that manager is going to talk to his friends (i.e. his network) about his bad experience and as a result others are not going to want to hire graduates from that school either. Even if it was bad luck, the fact remains that that guy made the whole school look bad to the manager and his whole network. Fair or not fair, that’s how the world works.</p>
<p>That’s why it’s better to have no reputation at all than to have a bad reputation. Yes, most jobs are relatively easy such that even a mediocre grad will probably not be found out. But sometimes they do get found out, and when they do, they make their whole school look bad. Fair or not fair, that’s how it is.</p>