So I've had a rather interesting conversation recently that I thought I would share, as it's something that's piqued my interest, and has a touch of relevance with the ban on calling yourself a "professional engineer" in parts of Australia.
I say "interesting" - the conversation itself was boring (and kinda dumb, actually) - it'd be more accurate to say that it prompted some interesting thoughts about semantics.
First up, some background info - skip ahead if you can't be bothered
I was talking with my boss earlier today about a display I built for the boom on the
sub-arc rig - nothing too complex, it's ultimately a fancy voltmeter that you can change the units on.
Because the control console is right beside the head, it has to contend with the EMI from the welding arc (for those unaware of the sorts of energies involved... our procedures call for an arc between 20v and 85 amps, to 40v and 600 amps (and all values in between) - which happens to be a ton of energy - pfft, you can even melt steel with it!).
Anyway, so I added a ton of filtering to it to avoid my display going crazy when the arc is struck - and right before installation, I ran some tests to make sure my filtering was working correctly and announced that it was ready to install to my boss, who claims to have been an electronics engineer.
He insisted on coming out because wanted to have a look at my design. A bit odd, I would rather he looked at my design
before I actually built it and tested it... but I figured he had his reasons, even if he just wanted to see what I had built.
The conversation didn't go that way...
"What's that?" he said, pointing to a TO-220 package with some inductors and capacitors sitting beside it - all on a daughter board
"That's just the PSU - I made it modular so we can change it out if we have problems with EMI"
"Ah okay... but what's this part?"
"That's the voltage regulator, pretty sure it was a 7805 I went for?"
"Yeah but what's it do?"
"It... regulates the voltage?"
"What do you mean?"
"It... helps smooth out the voltage spikes we get on the supply rail when the arc is struck - there's a ton of EMI from it"
"Ah okay..."
Then he walked away, looking a little confused... though not as confused as I was! "What was it (a voltage regulator)
for" - surely an electrical engineer would
know that it... regulates the voltage?
Maybe I had made a wrong decision? I'm only a novice, you see, so I question myself often - so I looked over my notes - I had a 5.2V supply rail to work with - it was noisy and spiky... so I filtered that out and was left with a ripply 5.2V, so I added a smoothing cap and the 7805 to give me a nice smooth supply rail to work with. My sensors were analogue, and the microcontroller ran at 4.5-5.5V so a voltage reg seemed obvious?
So, from my admittedly novice engineering perspective... things seemed alright? But the more I thought about it, the more something seemed off about the whole conversation... so I took to the internet... Where I promptly I discovered his "electronics engineering" experience consisted of soldering knobs onto toasters.
Not to belittle him of course, but if that was the sole bulk of my experience, I would
not call myself an electronics engineer... toaster engineer?
Maybe, but even then, there was no engineering involved!
See, from a strict linguistic standpoint, an "engineer" is anybody who does engineering (which appears to be loosely defined as anybody designing and building something... (and people who specifically operate engines)), but when you put this into practice, you'll find it often feels incorrect to call many of the people who are doing engineering
engineers.
The "problem" (I use this in the loosest sense of the word) seems to be the disparity between
descriptive and
prescriptive language - but it is best highlighted in some simple examples: which of these would you say was acceptable to refer to as an engineer?
- A student of engineering. They do engineering as part of their course.
- A student of engineering, working in an engineering capacity, on work-placement, as part of their course.
- A student of engineering, working in an engineering capacity, outwith their course.
- A graduate of engineering, currently unemployed.
- A graduate of engineering, employed, but in an entirely non-engineering sector
- A graduate of engineering, employed in an engineering capacity, but their job title does not include the word "engineer"
- A graduate of engineering, employed in an engineering capacity, but their job title includes the word "engineer"
- A hobbyist, who engineers as a pastime.
- A hobbyist, who engineers as a pastime, and is employed in an engineering capacity
- A graduate, who engineers as a pastime, but is not employed as an engineer.
Put simply:
- Do they have to be a graduate?
- Do they have to be employed as an engineer?
- Do they need to have "engineer" in their job title (or description)?
- Do they merely have to practice engineering (on a regular basis)?
- Can a hobbyist ever call themselves an engineer if they do not do it professionally and have never studied it at university or college?
Obviously, we can simply describe
how we engineer - for instance, "I do electrical engineering as a hobby" - or "I have a job doing electrical engineering" - or "I am a professional electrical engineer, but not in Victoria"; which circumvents the semantics issue, but doesn't really address it.
What might your thoughts be? As a novice-of-electrical-engineering-but-probably-not-an-engineer, I'd love to hear the opinions of actual-engineers on the matter!
--EDIT--
Ps - I know the application of the term is probably quite subjective - I might, if pushed, call myself an "amateur electrical engineer" in much the same way that I'd call myself an "amateur radio operator" - but I'd rather be unambiguous and describe myself as
doing engineering, rather than
being and engineer!