TuxDave
Lifer
- Oct 8, 2002
- 10,571
- 3
- 71
MS EE, started doing microprocessor design for 7 months. The basic routine is as follows.
Step 1) Read RTL
Step 2) Build circuit block
Step 3) Simulate circuit
Step 4) Repeat until fast enough
Step 5) Learn that your neighbors are too slow so you gotta speed up (repeat 2 to 4)
Step 6) Repeat Step 5 a couple more times
Step 7) Learn that RTL has changed... go back to step 1.
Hope that didn't scare you away. It's not too bad, just kinda time consuming.
Step 1) Read RTL
Step 2) Build circuit block
Step 3) Simulate circuit
Step 4) Repeat until fast enough
Step 5) Learn that your neighbors are too slow so you gotta speed up (repeat 2 to 4)
Step 6) Repeat Step 5 a couple more times
Step 7) Learn that RTL has changed... go back to step 1.
Hope that didn't scare you away. It's not too bad, just kinda time consuming.
Engineer
Elite Member
- Oct 9, 1999
- 39,230
- 701
- 126
BSEE - 1993: University of Kentucky College of Engineering
Work for an automotive supplier (tooling plant). We build the production equipment to make the automotive parts. I'm an automation engineer who's job is to design the electrical system and program/debug the final product.
I work with various levels of pneumatics, hydraulics, computer, PLC (programmable logic controllers), servo drives, sensors (capacitive proximity sensors, inductive proximity sensors, fiberoptic sensors, etc), touchscreen interfaces (including all programming), analog readings, heater controls, robot setup and full programming, and many other areas of controls and automation.
Have been working there since 1992, but went full time in 1995 (took 1.25 years for them to get approval to bring me on full time).
The work can be long (just completed a stretch of 84.8 hours a week for 7 straight weeks), but it's very rewarding work (getting paid OT helps too!
)
Automation engineers may be in need in the future as the US tries to switch from a manufacturing economy to something else, and the use of automation to replace (sometimes sadly) the manual labor in the remaining US factories. (Better than shipping it all overseas though).
Work for an automotive supplier (tooling plant). We build the production equipment to make the automotive parts. I'm an automation engineer who's job is to design the electrical system and program/debug the final product.
I work with various levels of pneumatics, hydraulics, computer, PLC (programmable logic controllers), servo drives, sensors (capacitive proximity sensors, inductive proximity sensors, fiberoptic sensors, etc), touchscreen interfaces (including all programming), analog readings, heater controls, robot setup and full programming, and many other areas of controls and automation.
Have been working there since 1992, but went full time in 1995 (took 1.25 years for them to get approval to bring me on full time).
The work can be long (just completed a stretch of 84.8 hours a week for 7 straight weeks), but it's very rewarding work (getting paid OT helps too!
)Automation engineers may be in need in the future as the US tries to switch from a manufacturing economy to something else, and the use of automation to replace (sometimes sadly) the manual labor in the remaining US factories. (Better than shipping it all overseas though).
IHateMyJob2004
Lifer
- Sep 29, 2004
- 18,656
- 67
- 91
bachelors in EE and math.
I am not practicing either degree.
I went into EE with an interest in the science and gadgetry.
I am not practicing either degree.
I went into EE with an interest in the science and gadgetry.
I just graduated in May, with my Computer Engineering degree, basically the same as EE, I work for a company that makes industrial control panels for companies like GM, Ford, Chrysler, Owens-Corning, and the like, I enjoy the work alot, basically I program control systems, and design industrial circuits and panels.
I was an EE major but im switching to Business Finance now. Through my classes I see that there were many great number crunchers in the bunch. I however, had a little more shapely developmental triangle. Still thinking of going in the generic technology field (work for a tech company) because I understand lots of what engineering is.
Anyways from somebody already in the workforce, heres what is what he said.
"A degree is simply a document stating your not a dumb ass, where you get your degree usually adds to the validity of this document. You may learn some analytical stuff and little technical stuff in school, but everything that matters is on the job training. If your an engineer and you speak english, your of very high demand, if your an engineer, speak english and can tell a joke or two and have the under average manager laugh at it, your probably going to be hired"
From what I gather, just like going through the public education system, college is almost worthless.
On the job training...an ee graduate can't really design a cell phone can he? He's smart enough to work in a group too do it...but thats all on the job training.
Anyways from somebody already in the workforce, heres what is what he said.
"A degree is simply a document stating your not a dumb ass, where you get your degree usually adds to the validity of this document. You may learn some analytical stuff and little technical stuff in school, but everything that matters is on the job training. If your an engineer and you speak english, your of very high demand, if your an engineer, speak english and can tell a joke or two and have the under average manager laugh at it, your probably going to be hired"
From what I gather, just like going through the public education system, college is almost worthless.
On the job training...an ee graduate can't really design a cell phone can he? He's smart enough to work in a group too do it...but thats all on the job training.
Thanks to everyone that has replied so far. I appreciate the responses. Hopefully a few more people will be able to see this and take the time to reply.
Sunday night bump.
Sunday night bump.
I graduated with my BSEE last november.
Before I had graduated, I had:
soldered circuit boards for production
tested those boards
troubleshot those boards
layed out the PCB for the next generation product
wrote code for the next generation product
designed a simple RF circuit
translated schematics between different capture programs
The first 5 were at a tiny company, the last two were at two different large aerospace companies.
Since I graduated, I've been doing production and test equipment support, meaning that I troubleshoot our product and the automated test equipment. Very shortly I'll be doing simulation and verification of VHDL.
The more you can do before you graduate, the better.
Before I had graduated, I had:
soldered circuit boards for production
tested those boards
troubleshot those boards
layed out the PCB for the next generation product
wrote code for the next generation product
designed a simple RF circuit
translated schematics between different capture programs
The first 5 were at a tiny company, the last two were at two different large aerospace companies.
Since I graduated, I've been doing production and test equipment support, meaning that I troubleshoot our product and the automated test equipment. Very shortly I'll be doing simulation and verification of VHDL.
The more you can do before you graduate, the better.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter