A mechanical engineer told me Science isn't useful?

Click For Summary
SUMMARY

The discussion centers on a mechanical engineer's assertion that science, particularly physics, is not useful in practical engineering contexts. Participants argue that while engineers often focus on the "big picture," scientific principles, including friction and fluid dynamics, are essential for effective problem-solving. The conversation highlights a disconnect between theoretical knowledge and practical application, emphasizing that engineering is fundamentally rooted in scientific principles. Many contributors assert that dismissing science undermines the foundation of engineering practices.

PREREQUISITES
  • Understanding of basic physics concepts, including friction and fluid dynamics.
  • Familiarity with engineering principles and their application in real-world scenarios.
  • Knowledge of the relationship between theory and practice in engineering disciplines.
  • Awareness of historical engineering practices and their evolution over time.
NEXT STEPS
  • Research the role of friction in mechanical engineering and its impact on design.
  • Explore the principles of fluid dynamics and their applications in engineering projects.
  • Study the historical development of engineering practices and their reliance on scientific theories.
  • Examine case studies where theoretical knowledge significantly improved engineering outcomes.
USEFUL FOR

Engineers, engineering students, and professionals in technical fields who seek to understand the importance of integrating scientific principles into practical applications.

physicsdude30
Messages
14
Reaction score
0
I talked to a mechanical engineer the other day, and he said "Science and physics isn't all that useful." :confused::confused:

I'm curious what a good response to that would be?

He said when he works on his projects, the "big picture" is the project, and Science and other aspects are only small details or parts to the whole. He said physics ignores very important details when he works on his projects, such as "friction", etc. He said if you get lost in the details like physics you'll miss the forest from the trees. He said, "We'll leave theories and hypotheses to the physicists. I'm a no nonsense type of guy who likes to be practical. If something's not useful and is 'theories', I don't care."

Any ideas for comebacks?
 
Engineering news on Phys.org
physicsdude30 said:
I talked to a mechanical engineer

There's your problem!

*runs and hides*
 
Any ideas for comebacks?
If a machine isn't working does he look for evidence of damage to a part? Does he try running the machine after removing/replacing certain parts?
or does he just roll dice to work out what's wrong?
That's science.

On the other hand, in most of fluid dynamics, aerodynamics and some parts of stress calculation I would rather have a large engineering safety margin than a 'theory' which assumes a spherical horse running in vacuum!
 
physicsdude30 said:
... He said physics ignores very important details when he works on his projects, such as "friction", etc. ...

:confused:

I'm sorry, but I have a hard time believing anyone with an engineering degree would make a statement like that. Perhaps he was joking? If he wasn't, I'm going to go ahead and say that he was talking out of his rectum.
 
physics ignores very important details when he works on his projects, such as "friction"
If he said physics textbooks/lectures/students ignore details like friction he would be perfectly correct (at least at an undergrad level)

How many questions about projectiles do you get here that ignore air resistance?
 
mgb_phys said:
If he said physics textbooks/lectures/students ignore details like friction he would be perfectly correct (at least at an undergrad level)

How many questions about projectiles do you get here that ignore air resistance?

So calculating fluid, sliding, and rolling friction are exclusive to engineering problems? Does one not learn about friction in classical mechanics?

Edit: I think I'm just having problems with the choice of words. To me, given that engineering is just a sub-discipline of physics, his statement sounds similar to an actuary claiming that mathematics ignores probability theorems.
 
Last edited:
Sounds to me like your friend is rather ignorant! It happens that people get preconceived ideas about certain subjects (though in this case, somehow, all of science..) and they just blanket believe it from then on: seems as though this is the situation your friend finds himself in, a remnant from a high school physics course he perhaps didn't enjoy.

Next time your friend tries to use GPS (I choose this for the sake of practicality, I think you could probably replace it with any object you can possibly think of), kindly remind him that, as a non-believer in science, he isn't allowed. General relativity doesn't like him either. :smile:
 
My, my. Is it possible that the OP has spoken to an ME with a talent for "human engineering" and has wrangled a job that requires no actual skill? I worked with such an ME about 25 years ago. He is an Indian engineer with tons of Dale Carnegie courses under his belt, and he treated people under him with absolute disdain. I can't think of any people (OK, maybe one) in that company that were more hated. He showed nothing but rudeness and dismissal to people that were doing their best to advance the goals of the company. If he ever gets to upper-level management in any company, I will buy derivatives betting against it in a heartbeat.

BTW: I apologize for going postal over a jerk so far back that many of you had not been alive then. At least you missed the experience. BONUS!
 
Last edited:
physicsdude30 said:
I talked to a mechanical engineer the other day, and he said "Science and physics isn't all that useful." :confused::confused:

I'm curious what a good response to that would be?

He said when he works on his projects, the "big picture" is the project, and Science and other aspects are only small details or parts to the whole. He said physics ignores very important details when he works on his projects, such as "friction", etc. He said if you get lost in the details like physics you'll miss the forest from the trees. He said, "We'll leave theories and hypotheses to the physicists. I'm a no nonsense type of guy who likes to be practical. If something's not useful and is 'theories', I don't care."

Any ideas for comebacks?

Sure: "You're a clown."

Enough said.
 
  • #10
I know an experienced electrical engineer that doesn't believe in quantum mechanics. After days of discussions and explanations, I gave up. I probably pissed him off too.
 
  • #11
what said:
I know an experienced electrical engineer that doesn't believe in quantum mechanics. After days of discussions and explanations, I gave up. I probably pissed him off too.


He didn't take a course in solid state physics? We were shown from the ground up with energy band diagrams and such.
 
  • #12
Hmm, this whole scientia sibi / scientia homini is a bit awkward to me.

What is practical use? makes life easier? why do we want life to be easier? to do more stuff we want to do, why? because we like to do those things.

Why do we practice pure science? because we like the search for knowledge as a hobby.

It's the same thing, the former is just for a person who has one hobby less than pure scientists, a pursuit of knowledge, the thrill of solving complex puzzles, if you like.
 
  • #13
tell him that if it wasn't for theories and hypotheses, even the steam engine wouldn't be possible. engineering is only the practical application of whatever science teaches us.
 
  • #14
1) You always run into a few who survived their college classes as opposed to actually learning the material. A lot of those just hope to wind up in a job that's not too challenging.

2) Quite a few of those still perform well on a job they've held for several years because experience is its own kind of knowledge. Quite a few nicely laid out designs just don't work because of variation in parts, etc. If you've seen enough similar problems, experience can be a good guide for determining which parts of the design most likely have to be tweaked. (That person is still going to have a hard time if he moves on into a new job.)

Even in classes, I've had a few circuits where the ideal values just don't work (mainly because your real parts don't have ideal values). The two options seemed to be to hopefully figure out which part(s) were the main cause of the problem, swapping new parts in and seeing what happened, and estimating what value for the key parts would give you the desired output - or grabbing several parts of the desired values and selecting only parts that are very close to the ideal values (that could get a little tedious with a lot of parts).
 
  • #15
Yeah, well, after the science is done, you need the engineers to engineer and write emails, then reengineer and write more stuff and rereengineer write a lot more emails, and someday they might get it right, but don't take it to the bank. 90% of them don't really engineer anyway, and you try to converse with them in the field in which they are titled it shows.
 
Last edited:
  • #16
chhitiz said:
tell him that if it wasn't for theories and hypotheses, even the steam engine wouldn't be possible. engineering is only the practical application of whatever science teaches us.

I think you have the cart before the horse. Modern Thermodynamics started with the study of how steam engines work (Carnot:Reflections on the Motive Power of Fire). Newcomen and Watt didn't use theory to design their machines.

For that matter, Engineers were building buildings and bridges for thousands of years before Statics was developed. The Parthenon and Chartres were built using nothing but rule of thumb.

I don't suppose that Electronics and Electrical Engineering could have gotten very far without the theoretical work of Maxwell et al, but even in this area, Edison didn't seem to have much use for theory. Even when you have a useful theory, a huge amount of trial and error goes into learning how to apply the theory. Remember the saying, "In theory, theory and practice are the same. In practice, they are not."

I suggest reading the book by L. Sprague De Camp, "The Ancient Engineers".
 
  • #17
joelupchurch said:
For that matter, Engineers were building buildings and bridges for thousands of years before Statics was developed. The Parthenon and Chartres were built using nothing but rule of thumb.
The Parthenon?

I thought the entire acropolis was supposed to be a work of mathematical perfection.
 
  • #18
Kajahtava said:
The Parthenon?

I thought the entire acropolis was supposed to be a work of mathematical perfection.

But which came first? The philosophers mathematical perfection? or the rules of thumb that worked so well?
 
  • #19
TheStatutoryApe said:
But which came first? The philosophers mathematical perfection? or the rules of thumb that worked so well?

It's one of the great stories of British engineering.
Britain's railways in the first half of the 19C, were built by illiterate northerners who didn't trust figures so just massively over-engineered everything. It's called a margin of ignorance - like a margin of safety.

The French however had the best engineering schools and the most brilliant mathematicians and they built bridges that were perfectly designed.
Unfortunately they didn't understand about things like stress concentrations that meant a material is only a few % as strong in real life as it is in the textbook.

The result (according to British engineers) is that lines built by Stephenson and Locke are still being used today, while everything built in Europe before Eiffel fell down.

It's not really true - but makes a good story.
 
  • #20
Kajahtava said:
The Parthenon?

I thought the entire acropolis was supposed to be a work of mathematical perfection.

The math was for esthetic purposes, not engineering. The Greeks had all sorts of ideas about what ratios and proportions were esthetically pleasing. The Pythagorean mystery cult also built all sorts for numbers into buildings they were constructing. You can see a lot of this numerlogy carried forward in Plato.

When I was taking number Ancient Architecture, when my professor was talking about the Pythagoreons in relation to a temple in Sicily. I pointed out that the temple had 6 columns on the short side and 13 on the long side which meant the spaces between the columns were 5 and 12. 52+122=132 which is called a Pythagorean triple. Oddly enough, no one had noticed that before.

http://en.wikipedia.org/wiki/Pythagorean_triple"

My professor ended up writing a paper about architecture and the Pythagoreons and I got a nice footnote in it.
 
Last edited by a moderator:
  • #21
hes a fool.
 
  • #22
You know what they call the person that graduates bottom of his Engineering class don't you?
 
  • #23
I've encountered quite a few "engineers" who believe that theoretical knowledge is useless in the "real world". These guys should take up plumbing and leave science/engineering to the smart kids.
 
  • #24
Brian_C said:
I've encountered quite a few "engineers" who believe that theoretical knowledge is useless in the "real world". These guys should take up plumbing and leave science/engineering to the smart kids.


I run a music venue. I generally do the sound.
It's a different field, but I have observed that people with degrees in sound engineering and music management have absolutely no clue how to do sound or manage business. In my observation, most of what they have learned is "under ideal conditions" that never actually exist in the real world.
 
  • #25
Galteeth said:
I run a music venue. I generally do the sound.
It's a different field, but I have observed that people with degrees in sound engineering and music management have absolutely no clue how to do sound or manage business. In my observation, most of what they have learned is "under ideal conditions" that never actually exist in the real world.

I think sound engineer in that context is like train engineer, or building services engineer.
 
  • #26
Galteeth said:
It's a different field, but I have observed that people with degrees in sound engineering and music management have absolutely no clue how to do sound or manage business.
Well, of course. One way that professors in engineering and science deal with students who have absolutely no business becoming engineers or scientists is to gently suggest they change their majors. "Oh, so you have an interest in music? Maybe you should think about a career in sound engineering or music management."

=================================

Back to the topic at hand: In a sense, the person referenced in the original post was correct. He/she was correct in the narrow sense of what knowledge is useful in the field of mechanical engineering. Most of the upper level undergrad and almost all of the graduate level courses that a physics major takes are more or less useless knowledge in the realm of mechanical engineering. Mechanical engineering is, for the most part, applied Newtonian mechanics, and I mean Newtonian mechanics strictly.

Even the sophomore/junior level classical mechanics course taken by physics majors isn't particularly useful to mechanical engineers because that course typically spends a good deal of time on Lagrangian and Hamiltonian formulation. Useless information! Then it wastes even more time (MechE perspective, of course) in deriving special relativity. Mechanical engineers live in a low-speed world of forces and torques.

So. Physics is not particularly useful to the everyday work done by working mechanical engineers. So, big deal. The person is over-generalizing from what is immediately useful to hima[/color] to what is useful to society as a whole.

---------------

a[/color]Yes, I'm being sexist, by saying "him", but years of work as a physicist-by-training, engineer-by-practice combined with a mental image of a hard-nosed, pointy-haired engineer combined with Bayes Law says that I'm probably right. That said, I have had two bosses in the past who emulated Dilbert's boss to a T. One was male, the other female. Women can be just as dumb, hard-headed, narrow-minded and as can men.
 
Last edited:
  • #27
Brian_C said:
I've encountered quite a few "engineers" who believe that theoretical knowledge is useless in the "real world". These guys should take up plumbing and leave science/engineering to the smart kids.

From my experience, a skilled plumber or electrician or machinist is valuable resource who should be listened to carefully. My father was a master electrician at the factory where he worked. The Chief Electrical Engineer would have his new engineers follow my father around to learn how to do their job.

Engineering is what you learn after you graduate from school.

A smart engineer knows to listen to the machinists or electronic technicians who are building his brainchild.
 
  • #28
physicsdude30 said:
I talked to a mechanical engineer the other day, and he said "Science and physics isn't all that useful." :confused::confused:

I'm curious what a good response to that would be?

He said when he works on his projects, the "big picture" is the project, and Science and other aspects are only small details or parts to the whole. He said physics ignores very important details when he works on his projects, such as "friction", etc. He said if you get lost in the details like physics you'll miss the forest from the trees. He said, "We'll leave theories and hypotheses to the physicists. I'm a no nonsense type of guy who likes to be practical. If something's not useful and is 'theories', I don't care."

Any ideas for comebacks?
I wouldn't bother with a comeback. That will not change his mind.

Science and physics are of course useful. Engineering is nothing more than applied physics, and practicing engineers and technicians practice their trade with the tools and methods developed by scientists and those engineers who understand the physics.

We apply theory and develop methods. One can't do one without the other.
 
  • #29
Astronuc said:
We apply theory and develop methods. One can't do one without the other.

Knowing how things behave in the world isn't the same as knowing why things behave the way they do. Reading some of the posts in this thread remind me of how Kepler developed his laws of planetary motion without any idea why those laws might be true.

In fact, not understanding the reason behind his laws is the reason it took him about 10 years to go from the first 2 laws to the 3rd law, in spite of the fact that the 2nd and 3rd laws are so closely related they're practically just different aspects of the same law.

Of course, that 10 year lag shows there are disadvantages to not knowing the 'why' behind the 'what', even if it's possible to function just knowing a lot of 'whats'.
 
  • #30
BobG said:
Knowing how things behave in the world isn't the same as knowing why things behave the way they do.
True, but knowing how works for a limited number of situations, especially if it's a periodic and repetitive phenomenon.

Knowing why a phenomenon happens allows one to extend the range of applicability.

If an engineer uses a tool or method that he or she didn't develop, it's because someone else learned the 'why' and developed the tool or method.
 

Similar threads

  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 7 ·
Replies
7
Views
2K
  • · Replies 17 ·
Replies
17
Views
4K
  • · Replies 75 ·
3
Replies
75
Views
16K
  • · Replies 14 ·
Replies
14
Views
3K
  • · Replies 11 ·
Replies
11
Views
2K
  • · Replies 0 ·
Replies
0
Views
457
  • · Replies 6 ·
Replies
6
Views
3K
  • · Replies 4 ·
Replies
4
Views
2K
Replies
13
Views
4K