<p>
[quote]
I'm not advocating that you teach all of them; just one of them, but don't teach none of them. Let's say your major is pizza making. The professor should teach the student how to make the dough and tomato sauce, and even how to fold a pizza box, but why teach this pizza making major how to weld? Wouldn't it serve the student better to learn how to cook chicken and broccoli? When is the student going to need to know how to weld when running a pizzeria?
[/quote]
</p>
<p>I feel a more appropriate analogy would be to teach what makes a good pizza and basic differences among the kinds of pizza (ie thin-crust, deep dish, stuffed crust, what the various toppings are) instead of just teaching them how to make only a good sauce and not anything about how to prepare a dough, what kind of cheese to use, and how to operate the oven.</p>
<p>
[quote]
Why do I need to understand Schrödinger's equation as a civil engineer? Can't I learn something else for the sake of learning? What civil engineering concept is derived from Schrödinger's equation? I'll make it easier. Show me a civil engineering textbook where the word "Schrödinger" is in it.
[/quote]
</p>
<p>I agree, you probably don't need Schrodinger's equation as a civil engineer. That's probably why CivEs at CMU didn't have to take the class. I think it's more of poor planning at your school that made you take a modern physics class than anything else. The only engineers I knew that were "required" to take modern physics were Materials engineers, and even we had the choice between Quantum Mechanics of Materials (a course actually developed by the physics department for engineers interested in modern physics), Biology I, or Organic Chemistry.</p>
<p>
[quote]
I think you just disproved your own point by stating how you used your knowledge of the colors of the various titanium ions.
[/quote]
</p>
<p>My point was that you never know what will be useful in your career, even if you think it's completely trivial information when you're learning it. I mean, I did a project based around stereology of grains, and I'm now working in a group that does amorphous materials (no grains), but I've still found instances where the knowledge has come in handy.</p>
<p>
[quote]
what's the point of that if, after the class, you never use them ever again?
[/quote]
</p>
<p>How are they to know what you will and won't use after you graduate? I took a class on semiconductor processing (a very industry-view centered course), and I haven't used my knowledge of Czarnowski since (I had to look it up for the correct spelling, even), but does that mean the class was a waste of time?</p>
<p>
[quote]
Again, I challenge anybody to explain what the heck any of the Maxwell Relations actually mean in a real-world sense. For example, what the heck does it mean for the partial derivative of temperature with respect to volume, at constant entropy, to be equal to the double partial derivative of internal energy with respect to volume and entropy. What does that mean in plain English?
[/quote]
</p>
<p>It means the change in temperature with respect to the change in volume for an isentropic process is equal to the change in internal energy with respect to volume and entropy during an isothermal and isobaric process.</p>
<p>See, the problem is, you're looking at Maxwell Relations which don't use easily measured values. By using Maxwell Relations along with the chain rule, you're able to get relationships between thermodynamic variables in things such as isothermal compressibility, thermal expansion coefficients, and things such as that. If we lived in a world where isentropic processes were common, then the Maxwell relations would be a lot simpler to understand. However, we don't, so you have to do some other crappy math in order to get it into more physically reasonable terms.</p>
<p>I agree, Maxwell's Relations are a bit of an abstract topic which are confusing, but if you're going to do any sort of higher thermodynamics then you need to understand what they are. To me, they're a nice artifact of calculus more than actually having a physical meaning. It's like asking an electrical engineer why e^(i*pi) = -1. Sure, they can tell you it's true, but what's the fundamental reasoning behind the mathematical meaning?</p>
<p>
[quote]
Hey, lots of things in life are good to know. But the real question is, what do you really need to know, and, more importantly, what do you need to know in order to avoid being weeded out of an engineering program? I would argue that if you are going to be weeded out for not knowing something, it should be because you don't know something that is actually important for being a practicing engineer.
[/quote]
</p>
<p>I'd consider fundamental calculus and physics to be things all engineers should have a pretty solid grasp on. The only people that dropped out of my major after first year (at which point I was actually the only declared freshman MSE) did so during our classes in crystallography and defects. You know, the stuff that everything in materials is based around (except for amorphous ones, ironically enough).</p>
<p>It would be more like flunking out an English major for not being able to write properly. Oh, wait, that's right, we don't do that. Colleges are supposed to just be degree mills where you pay some money and put in some time for a piece of paper.</p>
<p>
[quote]
Look, like I've always said, I'm not stopping anybody from taking the class if they want. You want to learn a bunch of theory that has nothing to do with being a practical engineer? By all means, go ahead and take all the classes you want. I'm not stopping anybody from doing that.</p>
<p>The question is, why do we need to force everybody to have to do it? That simply means that people are being forced to take classes that they don't want and aren't relevant to what they want to do.
[/quote]
</p>
<p>Why do philosophy majors have to take courses in all types of philosophy? Why do English majors have to take classes in all sorts of literature they don't care about? Why do abstract math majors have to take calculus?</p>
<p>Frankly, I feel like most of these weeder courses you're talking about are ones which happen very early on in one's college career, which is before most students even know what they want to study.</p>
<p>I agree the pain isn't something that's necessary in an engineering course; I think the pain is just an excuse that many engineering and science professors use to cover up for their own inability to teach well. It's kind of like how there are so few "good" textbooks for engineering out there. It's not that they're trying to make them bad, it's just that the people doing the writing aren't necessarily the best at their job.</p>
<p>So, yes, I agree that an engineering education shouldn't be painful, I think it's still very important to keep the breadth of the education and the focus on understanding the fundamentals of the technology instead of just teaching to whatever technology is current. Think about it this way. Do you think the best CS degree is one which teaches you how to be fluent in 20 computer languages, or one which teaches you very complex ideas and developmental strategies in one? And which one do you think will be better off 10-20 years down the road when all the languages they learned in college have become archaic?</p>