Im fairly new to the forum and have searched about what some of you guys do. I have a career specific question. Who all here is an Engineer?; doenst matter what, Civil, Mechanical, Electrical so on and so forth. I was curious as to know what engineers really do. And out of the classes you took in college (if you can remember) which one do you use the least? Im just curious to know as a hopeful future Civil Engineer. Thanks to everyone in advance.sd
Software Engineer here. Done quite a bit of embedded, and even a little GUI work (both in Windows and Solaris).
I've written specs, designed/developed/integrated/tested SW, operated test stands for sell-off testing of hardware (I was part of the team developing the test stand SW, so it made me a natural resource to help out on the testing), and even taken part in a couple of investigations into failures in the field.
As a result, I've managed to at least bump into nearly all my courses from school at one point or another. I've even had glancing brushes with thermodynamics (testing of HW was done over temperature cycles using LN2 to get to -20C) and materials (listening to the Mechanical guys making presentations about metallurgy and such), though I've not directly used either. Come to think of it, perhaps the only course I've not needed since getting out of school was Transport Phenomena (fancy term for a 1-semester course focused on the PN junctions that are the basis of the Transistor).
Now, you may be wondering where all this physical stuff is coming in, since I said I'm a SW guy. Well, my school (Stevens, in glorious Hoboken, NJ) pushes all engineering majors through a fairly broad core curriculum their first two years, giving you at least a little exposure to ME, Civil, EE, CS, Materials Eng., Chem, CAD, Engineering Management, and a few other odds and sods (such as an 8-semester humanities requirement). The idea is to make the students more well-rounded. As a result, I took the Computer Engineering path instead of a pure CS path (since I liked to tinker with things and I liked computers, but I "didn't want to sit in a cube all day writing code").
Guess what? I ended up in a cube writing code anyway, and I found out I liked it. Even better, since I've spent a good bit of my 12 years in the field being able to take what I write into the lab and get personal with the HW, I'm a SW guy who knows enough about scopes, DMMs, Logic analyzers, Spectrum Analyzers, etc. to be at least half way useful when something breaks. (as I put it some times, I'm not a Test Engineer, but I play one on TV sometimes).
My feeling on the matter is that I like having that broader curriculum to draw on - it gives me a better grasp of the system as a whole and how the SW's part plays with everything else. Put another way, it means when the HW guy wants something, I can grasp the
why as well as the
what.
Since it sounds like you're in school now or heading there, don't be afraid to toss some electives into your schedule from another discipline if you find something that catches your interest - being able to step away from your concentration and do something else for a short bit might be just the thing to break you out of a rut. In my case, I added a Minor in Music to my undergraduate Engineering degree (Have a BE and ME in my discipline), and I've taken four-course "graduate certificates of special study" in Systems Design and Operational Effectiveness and Project Management.