Well the topic pretty much says it all. What kind of enginner are you and why did you choose that?
Chemical Engineer. Betcha didn’t see that one coming. ;p Strangely enough, our second driver (there’s only us two) is also going into chemical engineering. Weird, huh?
yes, but how/why did you choose chemical?
You are not an engineer yet.
Software. It’s what my dad does, and it’s my hobby (and probably career too).
Who said you needed a degree (or even get paid) to be an engineer?
[edit]IMHO, it’s the achievement.[/edit]
Being part of an organization that’s expressed purpose is to raise awareness and respect for engineers and their work, I find it amazing that people are so quick to minimize such achievements and elevate themselves to similar, “iconic” status.
If one doesn’t need a degree (or a salary) or, say, experience to be an engineer, what is it exactly that makes people like Dave Lavery more admirable than the video store clerk down the street? I bet that clerk has seen MacGyver or something, so what makes Andy Baker more qualified as an engineer than they are?
A season in FIRST does not an engineer make. Not even six seasons will do it.
What the heck, I’ll say it. In my opinion, yes, you do need a degree to be an engineer. Don’t trivialize the process, tibulations and effort needed to get an engineering degree. I know very few engineers who do not have an engineering degree. They are few and far between, being exceptions, not the rule. What you said here pretty much insulted the engineers and engineering students who visit these forums.
As for me, I enjoy being a mechanical engineer. Luckily, I knew it early in school. I liked art, math, mechanical drawing, physics, and building things. I really did not understand electronics and computers at an early age, and I had no desire to learn about them… so I gravitated more toward mechanical systems.
Two of my uncles are mechanical engineers, and I was always enthralled with what they did. One worked for Hughes Aircraft (LA), and the other worked for Cal Tech at Edwards AFB. As they told me what they did, I just knew that being an ME was for me.
For college, I decided to go to the University of Evansville. They had many programs that appealed to me at the time. While in college, I got a co-op job at General Electric Plastics, working as a production and process engineer. I REALLY did not like process engineering (analyzing and tweaking the process for improvements), but I liked the odd jobs I got while designing mechanisms to improve the production line. I recall making a simple linkage that released pellets into 50 lb. bags. It was a simple design, but I really enjoyed creating it.
After college, I got a job at Delphi (formerly Delco Electronics) and I have been working in the same department for 13 years. It’s a fun job. I get to sit behind a computer and design automated machinery for Delphi’s production lines. Our design department works with a UAW skilled-trades shop right across the hallway, and we make some pretty neat stuff. These designers and tradesmen have been making neat machines for many, many years. Many types of automated machines that are on the market today (Scara robots, circuit board screen printers, automated handlers, flip chip placement machines, etc.) were developed for Delphi’s in-house use by this department, many years before other companies started selling them as standard equipment.
So, my usual day is this:
- check email
- do CAD design work (Unigraphics), both design and drafting
- do engineering investigations and evaluations (search for parts and suppliers, make calculations, specifications, etc.)
- check on project build status in the shop
- converse with boss and co-workers (numerous, informal design reviews)
- talk to production people (my customers)
- talk to suppliers (negotiate, evaluate parts, etc.)
- do FIRST stuff when I can (TechnoKats, check CD Forums, etc.)… like today we had a demo during lunch
Anyway… that is what I do and why I do it. What I like the best is sitting down and creating a new mechanism to address a “problem” - just like designing a FIRST robot.
Andy B.
[quote=Astronouth7303]Who said you needed a degree (or even get paid) to be an engineer?
If you REALLY want to get technical… Legally, in most states and definitely in NJ, the only real engineer is one who holds a professional engineering (PE)license. There are certain implications to what a PE can do, and situations where a PE is required. That being said, I don’t have one but have a bachelors and masters degree in engineering and think I can claim to be one.
On the original topic. I’m a Computer engineer by training, a Network and Telecommunications engineer by more training (i.e. Masters degree), and a Programmer by trade. I have to say my desire goes back to HS where I was luck enough to work in the local computer store in town. (in the days when a small 3 person store could exist before Best buy, the internet, etc) My boss was a person who enjoyed showing me things and getting me to help him. I have to credit him with fostering my enjoyment in electronics and computers that led to me study engineering in college.
So…not to be a party pooper…but in response to the thread topic
Andy Baker is a mechanical engineer (see post for what he does and reason why he likes it)
What type of engineer are you?
They had electricity back then? 
Dude, you are 16 and still in high school (I would assume unless you are some genious that has already graduated from college but I dont see that as the case at all). You are not an engineer. Just because your dad may be a software engineer does not automagically make you a software engineer as well. You are young and still have a long while before you mature. **
Andy Baker = engineer; Astronouth7303 = student.
**
[/quote]
I am a mechanical engineer.
I received my Bachelor’s of Science (B.S.) in Aeronautical Engineering from the United States Air Force Academy, a Master’s of Science (M.S.) degree in Aerospace Engineering from the University of Michigan, and a M.S. degree in Mechanical Engineering from the University of Michigan.
My first job was for the U.S. Air Force doing wind tunnel testing for what is now known as the F-22 at Wright-Patterson AFB. After receiving my Master’s degree, I worked for Lockheed-Martin in Sunnyvale, Ca. doing spacecraft design for the Air Force. I was transferred from Sunnyvale to Denver, Co. to work on NASA spacecraft; specifically, the Stardust Mission propulsion system design. Missing the MidWest, I came back to Michigan to work for FANUC Robotics (my current job). I have been with FANUC for 7 years and I love every minute of it!
My typical day is much like Andy’s, except I do a lot of mechanical and dynamic analysis of robot motion in addition to design work. I also get to test new robot developments for dynamic stability and accuracy. Lately, I have been able to finally use my fluid dynamics knowledge acquired while attaining my Aerospace degree because our group has been doing paint applicator development. We now develop the robots and the painting systems to paint automobile interiors and exteriors.
I have known since I was about 12 that I wanted to make complicated mechanisms. I, like Andy, wasn’t into the electrical side of things so mechanical engineering was for me. If I had to do it all over again, I would probably try to double major in controls and either mechanical or electrical engineering.
By the way; if you are in high school or in your first few years of College (studying engeineering), in my eyes you are not an engineer. I wish I could be more PC, but it is black and white to me.
I’m sorry, but I don’t think you get it.
You don’t measure up to someone with a PhD in Computer Science, and you aren’t doing well in comparison. It takes years of hard work to get a PhD. You need to discard a chunk of your life to reach that point. Say goodbye to your friends, family and hobbies for a while, because your life is consumed by your thesis. A PhD for some people is there entire life’s work. My Father finished his when he was 34. Just because you’ve written a couple of programs here and there does not put you on par with someone who has written a thesis. This is like a 15 year old saying, “ooh, I’ve finished all the experiments that came with my chemistry set, I’m a chemist now.”
The main goal of FIRST was to change our culture to a point where young people looked up to engineers as role models in the way they currently look up to athletes. How many little leaguers out there have the audacity to compare themselves to Derek Jeter and say “Oh yeah, I’m almost there”. This whole attitude is ridiculously insulting to all the engineers in the forum.
Oh and to be technical, having a PhD in Computer Science doesn’t make you an engineer either. Becoming a member of a society Professional Engineers does (In most states and provinces). By taking that oath, you’re taking on a huge ethical responsibility. This is a large distinction.
You may be on a path to becoming a fine engineer, but you still have a bit of time before you can call yourself one. You’re eagnerness and enthusiasm is certainly admirable, but remember it’s a long road.
“I have learned that engineering is not just creativity. It is not just tinkering with ideas, but rather, a system by which a professional product can be created and documented.”
That comes from the esteemed Dr.Christoe’s (aka Dr.Poe) PoE class. To those of you who know what Project Lead the Way is, you know what PoE is. Dr.Poe spent 23 years in engineering at Bell Labs, and before that he was a weapons engineer for a number of years.
At any rate, I can’t call anyone without a degree an engineer. I can’t even call some people with degrees engineers, as they would more properly fall into the categories of tinkerers and inventors. As Mr.Baker pointed out earlier, a lot of his time is spent in procedures supporting his inventing, not his inventing alone. I won’t say that the video game guy down the street is incompetent. He might have incredible talents with, say programming. He might have drafted up parts of the Linux kernel. None of that is impossible or even unheard of. Or if you follow Slashdot, recently they ran a story on a 60-odd year old Afghan man, who had invented many, many things to help people around him. He had no formal training, and yet was able to design radios. I would be very impressed to meet him, but I still woundn’t call him an engineer. I guess it all depends on how you define an “engineer”.
Before I started studying to become an EMT, I had very little respect for the area. Not because I thought that their work was so easy. Because I didn’t know the scope of the field. Now it is a completely different matter. I now realize how little I know. I know now that (in NJ) most of what I can do is, “oxygen and transport, oxygen and transport”. I realize that Paramedics are awesome, for their heart rhythm monitoring, intubation, and narcane. (In NJ, we don’t have any levels in between EMT-B and EMT-P).
Engineering is a professional field. Tinkering is a hobbyist one. Many FIRST teams I know of are engaged in the business of tinkering, not engineering. I don’t say that that is a bad thing or a good thing. Its just that they are separate. One can lead into the other, a master mechanical tinkerer might become a mechanical engineer through schooling/training. But they are separated by the vast abyss of obtuse and painful subjects, like Rigid Body Dynamics, Mechatronic Systems, Lagrangian Dynamics, Ballistics, and other complex fields.
The one thing I always loved about computers was the fact that one guy in the corner of his basement could theoretically write programs just as well as a full professional team. After learning more of PHP and perl, and meeting a monster called PHPTAL, I discarded those notions. I can write programs, but I am by no means a programmer. I can use a sledgehammer, but I am by no means a carpenter.
So, I have to pull out the white rabbit from this hat.
Would you trust your life to the heart dialisys machine Dean invented when he was about 20?
He has had no formal degree - (Dropped out of WPI remember), other than honorary ones. I know that is a stretch, but there are exeptions to every rule.
I mean no disrespect towards Dean either by mentioning that he has no degree, but you can be an engineer with no degree.
edit:I have to ask the question now. Do you consider Dean an Engineer or a spokesperson for engineering related fields?
Unfortunately in this world, if you are to work for a company and not become an independently wealthy individul from your abilities like Dean has, they do care about that piece of paper from your college…
I do agree with Paul that if you are in HS or your first years of college then you are not considered an engineer…
I mean I have been going to college for 7 years on and off now for an engineering related degree, and while I am very proficient in my skills as a CAD Draftsperson I am not by any means an engineer. I suck at math, and sometimes wonder why I am in the engineering field, but I do great things with CAD so that’s what keeps my hope alive.
Ok, anyways… I’m done ranting now.
For all of those HS students that plan on going into some sort of Engineering field, I wish you luck and hope that you achieve that goal and can be called an Engineer someday and have the respect and admiration that comes with that wonderful profession.
It’s black and white to pretty much everyone.
Watching ER on TV does not a doctor make you.
All these “kids” who think they’re engineers because they do FIRST, just need to realize they don’t know “crap” yet.
Let’s consider:
Step 1 - Think back 5 years, did you “know everything” back then?
Step 1.5 - Did you think you “knew everything” back then?
Step 2 - Think about now… do you “know everything” now?
Step 3 - What do you think you’ll know in 5 years? What will you think about yourself NOW, in 5 years?
My typical Answers:
- Wow, I didn’t know anything back then.
1.5. Ohh yeah… I thought I was the man back then. - Heck yes I know everything! I’m the man!
- Hmm… I guess in 5 years, I’ll realize I didn’t know anything right now.
It’s a humbling process. 
I’ve been in FIRST for 5 seasons. I’ve finished 3/4 of a degree in Mechanical Engineering. I learn something new everyday. I am NOT an engineer yet. I may work as one, but until I get that degree… I’m not.
Back to the real topic of this thread–
I’m majoring in mechanical engineering for several reasons.
Mainly because, mechanisms and machines are cool. Seriously.
I’m the type of person that will be (and has been) highly amused by an egg-beater.
(Seriously, check one out sometime, cool/simple little mechanism).
I have actually sat up at night, thinking about designs I’m doing at work, unable to sleep until I figure out the problem in front of me.
Go MechE… it’s fun.
Let’s consider:
Step 1 - Think back 5 years, did you “know everything” back then?
Step 1.5 - Did you think you “knew everything” back then?
Step 2 - Think about now… do you “know everything” now?
Step 3 - What do you think you’ll know in 5 years? What will you think about yourself NOW, in 5 years?My typical Answers:
- Wow, I didn’t know anything back then.
1.5. Ohh yeah… I thought I was the man back then.- Heck yes I know everything! I’m the man!
- Hmm… I guess in 5 years, I’ll realize I didn’t know anything right now.
Unfortunately, the same could be said for engineers with degrees. The feilds themselves are changing so much that you really need to constantly refresh yourself. So much so that I know to keep an engineering liscence in New York you have to prove that you are taking seminiars or collge courses. Also by the second year of college I will be working as an engineer. Im not sure what I’m going to be doing but I will be working.
Yep…
I was working as an engineer (or at least, working very closely with one) when I was a Junior in High School.
I wasn’t an engineer. I’m still not.
There is a distinction to make.
While the boundaries of being/not being an engineer are kind of fuzzy, here’s a great way to describe, in my opinion.
You have a degree: The university is giving you a piece of paper that says, “We’ve taught you a formal background in _______, therefore you can say you have the knowledge of many professors, other students, mentors, etc. Go out and use it wisely.” Afterward, as is true with all professions, you will learn more real-world applications and the tricks of the trade.
You don’t have a degree: You have no person or institution backing what you may or may not have learned. Your projects and examples are not as credible. While you may work with others and gain some experience, or may work in the position of what you’d like to be, you will not have the same benefits that one with a degree might have, especially if you have taught yourself.
I’m sorry. You are not an engineer.