if you are a mech engineer does it mean...

Older engineers seem to all have the same opinion of the younger ones. They're mostly a bunch of arrogant yet useless douchehammers that think they know everything. Further, my career plays a very small role in how I would describe myself so I actually prefer not to broadcast that fact to strangers. That's just me though.

Well for me, my career has a large influence on my geographic location for most of the time. Most people ask, not like I walk around telling every broad I am an engineer. Actually I prefer not to since I can't stand most engineering "types". But I am not ashamed to wear the ring either for fear of some negative connotation.
 
Well for me, my career has a large influence on my geographic location for most of the time. Most people ask, not like I walk around telling every broad I am an engineer. Actually I prefer not to since I can't stand most engineering "types". But I am not ashamed to wear the ring either for fear of some negative connotation.

That's sorta my point. But I include everyone, not just the 'broads'. I'm not ashamed of being an engineer, but I have been subject to that negativity and I'd prefer to avoid that bad first impression. Perhaps we just walk in different types of circles and as such it's not something you'd ever really experience
 
And yet so many of the things around you at any given time was designed by an engineer. Crazy how that happens.

There's a big difference between theory and application. For example mechanics have no issues following torque ratings but most would be lost calculating them.

In my original field (electronics) I would be consumed working demorgan theorems, calculating heat dissipation and R values, fan-out, propagation delay etc. Way beyond most technicians for troubleshoot components of the final design looking for the failed component. My first job was as a troubleshooter and I was lost, always over-complicating things, trying to figure out where the design failed...

Move ahead to today and almost nobody does board-level troubleshooting like that anymore, it's all component swapping and pretty much any trained monkey can do it... That's why I made the leap to software, where analytical skills and the ability to focus for long periods pay off.

Got a maintenance problem, take it to a technician/mechanic, Something wrong with the design, that's where you need engineers. Some may not be able to spin a wrench but, if a fresh approach is required....
 
I'm not ashamed of being an engineer, but I have been subject to that negativity and I'd prefer to avoid that bad first impression.
I experience both negative and positive reactions on first impressions and I've come to grips with it. If someone is that close-minded that they've "made up their mind" about me before getting to know me, it's their loss and not mine!

BTW, I'm not a douchnozzle (but I know a couple engineers that are!)
 
And yet so many of the things around you at any given time was designed by an engineer. Crazy how that happens.


Engineers also frequently design things that can't be build. Technicians, Technologists, and shop Foreman are the ones to get it to work, and built.
 
I did a mechanical engineering apprenticeship. I can take stuff apart. Sometimes I even get it to go back together. Most of the time I don't have any nuts or bolts left over.
 
What's all this ring BS? What's that all about? You get a ring if you're an engineer over here? Is it like a Superbowl ring? Does it squirt water?

At the end of my apprenticeship I got a job. And I kept it.
 
Engineers also frequently design things that can't be build. Technicians, Technologists, and shop Foreman are the ones to get it to work, and built.

If htere's a shop foreman involved, it sounds like your problem might be with the fabricator, not the designer. Just saying (as an engineer).
 
As a process engineer I got to see design engineers design impossible stuff.

The only way to create one weldment was to have a dwarf welder permanently weld himself inside.
 
As a process engineer I got to see design engineers design impossible stuff.

The only way to create one weldment was to have a dwarf welder permanently weld himself inside.

I was being shown round a new GM truck plant a few years back during the trialing and comissioning. One process/project engineer remarked to me that, in his opinion, automotive design engineers should be required to build the first 100 cars down the line and then drive them and work on them for a year as their primary means of trtansport.
 
As a process engineer I got to see design engineers design impossible stuff.

The only way to create one weldment was to have a dwarf welder permanently weld himself inside.

Everyone who designs anything has done something like this on occasion, whether they have an engineering degree or otherwise. Can't always see on a piece of paper or flat computer screen how it's going to be in reality. Solid modeling that will run on a computer that anyone can afford helps ... didn't have that back when I was designing stuff. Still doesn't help if the operator doesn't have a clue.

My theory is that everyone has a limit to the number of pieces that they can visualize going together in their head. We've hired (and subsequently fired) mechanical designers whose limit was one: they couldn't get two adjacent pieces to have the same bolt pattern on them. When this was pointed out to them, they'd just change it on that drawing, without addressing the repercussions downstream. Arrrgh ...

Been there myself ... Management was worried about how a certain workpiece was going to be clamped in a machine that we were building, which was my design. I wasn't worried about them, but that's another story. Management insisted on having extra clamps designed in (everything around this area had already been designed and most of the parts were already built). I drew them up but forgot about a certain major un-movable part of the machine that would be sharing the same space, and this wasn't discovered until the shop tried putting it together. Phone call, "get down here and have a look at this, what do you want to do?" Answer ... "Leave 'em out!" Ended up working fine without (as per the original design ...)

Sometimes it's an organizational deficiency ... We once subcontracted out the mechanical design of a heavy-duty conveyor system. Biggest mistake ever. I (project manager) had a certain date that I had to commit the locations of all the footings in the concrete. A few weeks before that date, the inquiries went out: "We need to know where you want your footings". No response. No drawings. No reaction. A few days before, the request was sent again. No response. The day before, "Tell me where you want your footings by date XXXXX, otherwise I'm going to tell you where they're going to be." No response. I spent that day drawing up where the footings were going to be, with no knowledge of the detailed design of that conveyor frame, and on date XXXXX, that drawing went out to the concrete contractor and to the conveyor designer.

Only after that, did I get a phone call complaining that they had to redesign the conveyor frame to fit the footings. "Too bad. Too late now. Deal with it."

That part of the project worked out in the end, but did it ever look messed up. Not much else worked out ... this was symbolic of the whole mess on that project. Ill-defined specifications, overly ambitious goals, committing to a project knowing that there were things we didn't know how to do, not enough money in the budget, not enough real estate, you name it. Company subsequently went bankrupt, but I was outta there before that happened.

I still see designs that are half-baked and not thought through properly, or in which the design that was implemented has been done for political reasons (to keep someone happy) even though it's not the right solution, etc. Most of the time the designers know full well that it's not right, but it's being thrust upon them by others, "thou shalt do it this way".
 
I think another thing that some forget is that you have to design a LOT of things in a shorter and shorter period of time in a thing that doesn't yet exist. Plus you have several to 10's of people who may be drawing what you're designing and they may make mistakes and you can't necessarily catch it all. For instance, my former company did the building design for a large auto assembly plant. For instance, on phase 2 (one of the two assembly buildings..) they had 2 electrical engineers working on that job plus an electrical project manager. They had about 4 months to do the initial design. Think about how big that building is.. And you rely on other subs..the assembly line guys have to provide data in good time in order to design the building correctly (footings for machinery like Brian's situation..electrical..mechanical..) and every delay is money.. You might like to think engineers are stupid, but a lot of time you have to cut corners to get stuff done and you deal with it later. Companies will pour walls without stamped drawings and no mech/elec drawings just to meet time bonuses which amount to millions of dollars. There's a lot going on.
 
Sometimes there's an underlying reason for something that seems dumb on the surface, too.

Had issues on a project a few months ago where a floor in a pit had a step in it for no visually apparent reason, and which caused all sorts of clearance headaches, tripping hazards, etc. Very tempting to ask "who the heck designed this - why isn't this just a level floor".

The problem is that this huge machine had to fit between the columns of an existing building, and the existing (HUGE) footings for those columns are right underneath that step in the floor. Digging out those footings was absolutely and completely out of the question ... so the pit had to be raised up above those footings along that side of the pit. Couldn't move the whole machine further away because then it would be up against the next column row. Couldn't raise the whole machine up (shallower pit) because then the existing overhead crane wouldn't be able to pass over (as it stands, it passes over with only a few inches of clearance!). Changing the crane is out of the question because that crane is HUGE, don't even dare raising the question of how much that would cost.

The world is not a perfect place, and you cannot have everything your way. Welcome to the real world.
 
Engineers also frequently design things that can't be build. Technicians, Technologists, and shop Foreman are the ones to get it to work, and built.


Interesting, we didnt seem to have any problems designing and building large motors for use on the bottom of the ocean floor for the oil and gas industry at GE.
 
Last edited:
I'm not an engineer, but I was in the trades and am considered extremely handy.
But I race a sailboat and seriously, we have 5 engineers in the program, everyone of them has an area of expertise but that doesn't mean the electrical engineer can fix the electronics on the boat, the chemical engineer can tell you much about the resin laminate layups the boat was built with or the process engineer "pharmacutical manufacture" can tell you much about any process we run.

There is a huge level of confusion with "laymen" that an engineer can figure out everything. They are probably pretty good in the area of industry they work in but that can be a pretty small area.

And one of the guys is a jet airplane mechanic, he's great with tools, he's also the reason I drive a lot of places.
 
Back
Top Bottom