<p>
</p>
<p>I don’t see this as the same issue. Rigor has nothing to do with practicality, as myself and monydad have pointed out. Like he has said (and I agree), the most rigorous classes are often times the most theoretical, which generally have little true real-world practicality.</p>
<p>This actually gets to yet another problem I see, which I hadn’t discussed much yet, but I will now. The truth is that many engineering programs are rigorous ABOUT THE WRONG THINGS. </p>
<p>Let’s use Berkeley as an example. If you just want to be an EE (not a CS or a CompE guy, just an EE), you still have to pass the notorious weeder Computer Science Data Structures class. This is a NOTORIOUS weeder at Berkeley. Yet the truth is, data structures has little to do with the actual tasks of a practicing EE. EE’s simply don’t need to know more than, say, the first few chapters of the data structures book (and probably not even that). Like I said, this is not CS we’re talking about. I agree that CS people should know data structures. This is EE. If you just want to deal with circuits or fiddle with electronic devices as your career, frankly, you don’t really need to know what a radix sort is. You don’t need to know what a splay tree is. You don’t really need to understand randomized analysis. These topics have nothing to do with what an EE actually does in his daily job. </p>
<p>Now, don’t get me wrong. Are these things nice to know? Sure. I have no objection to EE’s learning these things who want to learn them. But the issue is why FORCE them to learn it, when they don’t need it? And, in particular, why weed people out of a particular profession because they couldn’t understand something that, frankly, they don’t need to know for that particular profession? Why do that? That’s like saying that you won’t let somebody graduate with an English degree because they couldn’t speak Chinese. What you using to weed people with has nothing to do with the actual job. </p>
<p>And again, this also gets to the notion of the ‘academic engineer’. I know some engineering students at MIT that have absolutely stellar grades and are true geniuses. But I wouldn’t want them to be practicing engineers. Sure, they’re brilliant math geniuses, and that’s why they do so well in the highly theoretical engineering coursework at MIT. But I don’t think they would do well in an actual engineering JOB. Theoretical coursework and actual job tasks are not entirely consonant, and in some ways, are actually orthogonal.</p>
<p>So by making things more rigorous, especially at the top schools, you are simply eliminating more people who could be engineers and encouraging the creation of more ‘academic engineers’ - guys who can brilliantly do the math, but can’t actually do the job of engineering. For example, making EE more rigorous at Berkeley would inevitably mean raising the standards of the data structures course, which would mean that even more people who could be perfectly good EE’s would be thrown out of the program because they couldn’t do data structures, which they don’t need to know anyway. </p>
<p>
</p>
<p>Then you are saying that you disagree with what MIT does with its hidden freshman grades, and what Caltech does with its freshman shadow grades (which are basically another form of hidden grades), and what Stanford does in general (which is to hardly fail anybody out). Is that right? If so, then you should come out and say that these schools are wrong. </p>
<p>
</p>
<p>See, there it is again, so I ask you, what about all of those lower-tier, no-name schools? They are churning out engineers who are not as good as engineers coming out of MIT. These engineers might cause your GTA game to be delivered slow, or your apartment complex to be razed because of bad design. So are you advocating the shutting down of these lower-tier schools because they produce relatively lower-skilled engineers (relative to the average)? </p>
<p>Maybe you recoil at the notion of my calling them “relatively lower-skilled”, but, that’s the whole point of an average - that some are above average, and some are below average. By definition, 50% of the schools out there are “below-average”, and 50% of the engineering graduates out there are “below average graduates”. </p>
<p>
</p>
<p>And that’s where we are going to disagree. I don’t see the assignment of letter grades as part of the TA’s job. The prof can ASK for advice regarding the assignment of grades, and the TA is perfectly allowed to give it. But I didn’t see any evidence of this occurring. </p>
<p>
</p>
<p>And it is precisely this sort of reactionary attitude that with which I disagree. First off, who says that you can’t cut it? That’s an arbitrary distinction. A Berkeley grad who “can’t cut it” could almost certainly cut it at a no-name school. The notion of not being able to cut it at the top schools is therefore a purely arbitrary notion. Berkeley arbitrarily decides that the students are to meet a certain threshold, and if they can’t, then that means that they can’t cut it in terms of meeting that arbitrary threshold. It doesn’t mean that they can’t cut it AT ALL. </p>
<p>I’ll give you a poignant example. I know a guy at Berkeley who did extremely poorly in data structures. Yet the fact is, he actually has quite good knowledge of data structures. In fact, he had a part-time job tutoring data structures to some students at San Francisco State. So it’s not as if he didn’t know data structures. He knew it pretty well, and certainly better than the SF State kids did. The issue is that he didn’t know it well enough BY BERKELEY’S STANDARDS. But that is a purely arbitrary standard. Heck, if he had been going to SF State, he’d be cleaning up. </p>
<p>So when you say that somebody doesn’t cut it, I would ask “by whose standards”? According to Berkeley’s standard, he doesn’t cut it. By SFState’s standard, he easily cuts it. Yet neither standard is inherently more correct than the other. Whichever one you choose to adopt is a purely arbitrary choice. Hence, the notion of not cutting it is also an arbitrary distinction.</p>