Posted on September 6, 2008  Comments (6)

Guest post: What is an engineer? by Chris Gammell

I’ve been having what some would call an identity crisis. How, you ask? I’ve been working on digital electronics.

*GASP*!

I found out that in the early 90s and even earlier, analog engineers routinely switched from working in the analog domain to the digital domain…because it was paying really great. Not only that, most analog engineers had the expertise to do what most early digital engineers were doing (basically stringing together a lot of digital gates in DIP packages). It wasn’t until later that digital engineers started acting more as programmers and VHDL/Verilog experts.

So why do I bring this up? Because I’ve been thinking about the versatility required from engineers in general, not just analog or digital engineers. Routinely engineers are asked to switch modes or tasks or careers in order to get a job done. It’s not that other professions are never asked this; it’s just that the chameleon-like requirement placed on engineers seems to define the profession. Allow me to explain.

What is an engineer?

I think it is important to note that an engineer is different from a scientist, although the line can often be blurred (especially when looking back at the inventors of the early 20th century). In modern times a scientist is usually tasked with pushing the barrier and finding new theories and concepts. This means that the concept will not necessarily be available in product form right away (although this is not always the case), as the product form must be iterated upon and improved for production.

Another interesting point is how the above definition manifests itself in higher education. When I was in school, the focus was definitely on making engineering scientists, that is engineers who are taught to research new methodologies and concepts with the final product in mind. There was much less focus on using existing products (i.e. discrete transistors) to create something new or to solve a problem. I do not think that it is a huge problem, as some of my classmates went on to work on their Master’s degrees or to work in research labs. The rest of us trying to break into industry were a little more strapped on what is expected from an engineer. Let’s go over what some of these things might be.

1. Flexibility — This could be a theme of this article. Engineers have to be flexible and think on their feet. Again, I’m not saying scientists and other professions do not have to do this, only that it is required for many engineers. I went into my first job (working in a fab) as an electrical engineer student and ended up looking at chemical reactions and doing process engineering. The company I worked for didn’t want an electrical engineer, they wanted an engineer, someone they could teach their methods to and who could pick up the nuances as quickly as possible. I think it’s also important to note that they didn’t just hire engineers, they also hired scientists (don’t worry, I like scientists).
2. Science and math knowledge — No surprise here, you have to know the basics in order to really get going in the field. However, I think that the interesting thing is that the basics is usually the majority of what you need. I used Ohm’s Law more often in practice than I use the knowledge of how to do the third integral of a sphere.
3. Design re-use and not trying to re-invent the wheel — This was actually the reason I wanted to write this post, to point out that engineers often enter the field thinking they will be designing every piece of a system from the ground up. First off, this is irresponsible. The industries would never have standards if every engineering firm was trying to redesign a buck-boost converter everyday. Instead, engineers use optimized solutions available from vendors. Not only does it help standardize, it saves time.
4. KISS — This directly relates to the above point. You have to keep it simple, because there are only 24 hours in a day. I have claimed to be a system designer before (or at least will be). To design a full system, you have to look at the simplest and fastest solutions because they are often the best and most elegant solutions. Not only that, if you don’t do it as fast and simple as possible, someone else will, and then you’ll lose out on a customer, contract, etc.
5. Learning is pain — Even though continual learning is one of the main reasons I got into engineering, it’s not always fun. It’s not a great feeling when someone asks you to do something and then you have to slink away because you have no clue how to do it. Hopefully you’re slinking to go learn about it and not running away, but that is dependent on the person. The point is, learning is a difficult process and we really learn the most when we’re in situations that stretch us to the limits. In my experience, I always learned more in classes where I worked to get a C than in the ones where I breezed by and got an A.

Engineering is a field I entered because of the myriad things I could work on throughout my career. I did not switch to the digital domain for the money. I switched to digital work because I was asked to and it has been really interesting so far. Programmable logic is something I’ve worked on in the past and something I’m sure will become more prevalent in the workplace as design requirements become more stringent and timetables get shorter. If you are an engineering student or an aspiring engineer reading this article, I would highly suggest the profession (just make sure you note the above points). If you’re an experience engineer, please feel free to leave your experience in the comments. Thanks for reading.

Chris Gammell 24 year old engineer from Cleveland Ohio who publishes
the Chris Gammell’s Analog Life

Related: Open Access Education Materials – Engineers Should Follow Their Hearts – S&P 500 CEOs, Again Engineering Graduates Lead – posts on engineers