Another way to look at engineering that I like is that engineering is creative.I know there are engineers that are mostly involved in operations and maintenance, but those activities can require creativity at times.
I have had the wonderful opportunity to work in design in the spacecraft and many other industries where what you are doing has never been done before.This really brings out creativity in engineering.On one project we had a group of PhD Physicists whose job title was phenomenologist.They were there to answer a specific question about what the system we were designing was meant to deal with.Their role, as with many scientists doing science, was to describe nature.That can be very challenging.Often though, to do that they have to design instruments, etc.That is really engineering, not pure science.
Rob, you are so right on with that comment. My father was a designer at a government electronics lab. He always stressed the ability to write for engineers. He saw too many of the engineers he worked with getting little or no credit for their ideas because someone else had to be brought in to write them up.
Hi TJ, I'm delighted you included "a writer" in your list of the disciplines required of an engineer. As a journalist covering engineering, I've long been impressed by the writing skills of engineers. Of course that may be engineers who took their high school and college education at a time when writing was emphasized for all disciplines.
T.J., this is a great concise summary of what engineers do. I might add "negotiator" (working with manufacturing, purchasing, etc. in order to balance their needs without sacrificing product performance), and sometimes "policeman" (making sure that everything is being done according to the design specification).
For those of us who work with legacy designs, you could also add "historian" -- reviewing design history to see why a particular decision was made, or how a particular problem was tackled in the past. (Depending on how far back the legacy designs go, "archaeologist" might be a better term for this).
The common theme underlying all of the roles you mentioned is problem solving. It's worth nothing that, even though the problems we are tasked with solving are technical in nature, it takes more than just technical skills to solve them. In spite of the stereotype of the antisocial engineer, it actually takes a lot of people skills, too.
I like the Swiss Army knife analogy, TJ. And I think today's engineers have an ever-expanded palette of disciplines, methodologies, and specialty areas that they are expected to be versed in for problem solving. That said, what specific skill areas do you think are ever more critical to have in the engineer's so-called knife repetoire?
In an age of globalization and rapid changes through scientific progress, two of our societies' (and economies') main concerns are to satisfy the needs and wishes of the individual and to save precious resources. Cloud computing caters to both of these.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.