<p>
[quote]
I am one of those guys who might say what you mentioned isn't 'real engineering' (it could be argued but that's another point)
[/quote]
</p>
<p>I knew somebody was going to say that, which is why I then presented the example of electrical engineering, of which I can give you more instances. For example, as a new EE today, you probably don't really care about how a CRT works, because the entire TV industry is clearly moving to flat-panels. Only a tiny percentage of EE's will ever need to care about how vacuum tube diodes work, because with the exception of extremely-high-fidelity audio, nobody uses that stuff anymore; it's all been replaced by integrated circuits. Similarly, fewer and fewer EE's will ever need to care about analog electronic media storage devices such as audio tape decks, VCR's, and so forth, because it's all being replaced with digital storage. Take broadcast TV transmission: after next year, EE's in the United States will never have to care about the current broadcast analog TV transmission modulation standards because by law the entire country is being moved to broadcast HDTV. Or how about phone switching technology? Fewer and fewer EE's will have to care about how the venerable Class-5 central office phone switches work because phone services are all inevitably moving to Voice over IP. </p>
<p>Now, I would argue that all of these technologies are 'real engineering' by anybody's standards. But that just demonstrates that much of EE is extremely innovative. {Now, granted, other subdisciplines of EE, such as power generation, are not highly innovative.} </p>
<p>
[quote]
Regardless of whether or not the older body of knowledge is not necessary, the fact is that we engineering majors still have to take those courses
[/quote]
</p>
<p>Yeah, but that begs the question of why? Specifically, why exactly do they have to take so many courses? Like I said, to use CS as an example once again, you can become a competent software developer even if you've never taken a single college class - heck, even (like some people I know) if you haven't even graduated from high school. So why exactly do CS programs force students to take all these courses that they don't really need to know in order to do the job? </p>
<p>
[quote]
I will say that as a chemical engineer major, I realize that it is essential to understand the foundations of it. We are chemists, but we know enough chemistry to understand to some degree what is happening so that we can communicate to chemists who may work with us. We have to know heat transfer and about mass/material/energy balancing because these form the core- without it we will be loss as technology advances
[/quote]
</p>
<p>The question is not so much whether you will need to know these topics at some basic level. The question really is about how deeply do you really need to know them. </p>
<p>I'll give you a case in point. To this day, I still don't really understand what the heck the Maxwell Relations really mean. Or, on a similar note, what exactly is the difference between, say, the Helmholtz free energy and the Gibbs free energy. Now, granted, I can tell you the formulas, I can do the math, but I still don't know what it really means.</p>
<p>Nor was I the only one. For example, I know one girl who graduated with high honors, stayed to get her PhD, and then was offered a TA position for that very same chemical engineering thermo class that she took as an undergrad But she felt she had to turn it down because she said, frankly, that before she could take that position, she would first have to actually know that stuff. So here's a person who actually did extremely well in the program - enough to get admitted to the PhD program and complete it in just 3 years - yet even she admits that she doesn't really understand ChemE thermo. </p>
<p>That's why I'm convinced that chemical engineering thermodynamics is just an unnecessarily obscure and obtuse topic. Even the very best students don't really know what the heck is going on.</p>