Skip to content
View in the app

A better way to browse. Learn more.

New Jersey Gun Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

You Don't Have To Be An Engineer To Appreciate This Story

Featured Replies

So, is it the engineer's fault when the installer (technician, union duct fitter, what have you) installs the vav box, electric heater, or ATC panel in such a way that the access door can never be opened?

 

of course. if mr engineer was so smart, he'd have engineered it to make it impossible to install that way. :D

i've driven 60's mustangs, and cougers, 70's ford and chevy pickups, and ford station wagons 80's mustangs and crown vics through all sorts of nasty weather. the only time i ever had any of my vehicles stall due to water, was when i landed in the puddle that was a little deeper than i though. like 4 feet deeper, lololololol. had to get towed out of that one by a ford. :)

 

I had to clean out the distributer after this one, Woulda made it too if she didn't stall out !

 

281934_1852393795079_6272350_n.jpg

Engineer, Installer, Tech.... Not always the same thing. We had all three. But IF the installer did it to the Engineer's spec and was fubar, that usually was the Tech's job to fix it... At that point, I traveled back up the ladder to the top. If the installer was clear, then eng. was next to get crapped on... I was an electronic tech and out of all the engineers I met, there was only one I met that could talk turkey on the same level and vice versa.

 

And you know why this happens all too often? Because the engineers refuse to talk to the guys in the field... They use their knowledge which could be sound, but they have no clue what all the after affects are outside his lab. They need to talk before design.. Hash things out and then design.

 

 

:maninlove:

 

You know what I mean, Engineer, installer, whatever ! Somebody else making my job harder.

 

 

Sent from John's iPad 2 via Tapatalk HD

Typos courtesy Apple...

And you know why this happens all too often? Because the engineers refuse to talk to the guys in the field... They use their knowledge which could be sound, but they have no clue what all the after affects are outside his lab. They need to talk before design.. Hash things out and then design.

You couldn't be anymore right....

At my plant we don't have an engineer....

I am my own engineer, I design all my own projects in a 3D drawing or mentally.

I do the R&D, I do the trial runs.... I install and maintain all the equipment on a daily basis.

I was an electronic technician for a few years and industrial electrician for a few more... I've worked closely with engineers in multiple fields.... Out of my years doing this, I may have worked with 1 or two engineers that see the bigger picture. How available are replacements parts when... Not if it breaks.

How accessible is it to maintain properly...

What level of training is required to teach someone to operate or maintain..

There's a lot more to it than just design and implementation. Most engineers don't see past design.... Some do though, and those are who I stick close to and learn from.

It really helps to start out your way...

We had salesman that only saw dollar signs. They'd sell anything to get a contract whether wrong or right. I tried getting the company to never put a salesman in the field till he/she worked the tech field first. On the same concept, an engineer should be a tech first. Installers, well... They didn't give a crap at all most of the time. Knowing it was wrong to install it the way it was laid out, they'd install it anyway and walk away saying, not their problem. I use to go ballistic!

I can only say, if these ideas went in the correct order of education, there'd be a helluva lot less problems afterwards in a long run.

 

You couldn't be anymore right....

At my plant we don't have an engineer....

I am my own engineer, I design all my own projects in a 3D drawing or mentally.

I do the R&D, I do the trial runs.... I install and maintain all the equipment on a daily basis.

I was an electronic technician for a few years and industrial electrician for a few more... I've worked closely with engineers in multiple fields.... Out of my years doing this, I may have worked with 1 or two engineers that see the bigger picture. How available are replacements parts when... Not if it breaks.

How accessible is it to maintain properly...

What level of training is required to teach someone to operate or maintain..

There's a lot more to it than just design and implementation. Most engineers don't see past design.... Some do though, and those are who I stick close to and learn from.

 

 

Sent from John's iPad 2 via Tapatalk HD

Typos courtesy Apple...

It really helps to start out your way...

We had salesman that only saw dollar signs. They'd sell anything to get a contract whether wrong or right. I tried getting the company to never put a salesman in the field till he/she worked the tech field first. On the same concept, an engineer should be a tech first. Installers, well... They didn't give a crap at all most of the time. Knowing it was wrong to install it the way it was laid out, they'd install it anyway and walk away saying, not their problem. I use to go ballistic!

I can only say, if these ideas went in the correct order of education, there'd be a helluva lot less problems afterwards in a long run.

 

 

 

 

Sent from John's iPad 2 via Tapatalk HD

Typos courtesy Apple...

I wish it was always as simple as a educational progression up the ladder.

My boss ( maintenance supervisor) has never worked in maint. A day in his life. He was a machine operator for 20yrs. He knows how to make a glass bottle, he doesn't have a clue what it takes to make a reliable machine that makes the bottle.

He has no prior experience with scheduling pm's, organizing a shutdown to overhaul a machine. Prioritizing breakdowns, or inventory. He tells us one thing, and shortly after asks us why we are doing that and not this....

Frustrating doesn't even begin to describe a typical workday.

I have a list of back work to complete, but can't get the time to do it because he piles more crap on us shop guys.

He had the task of designing a machine off of memory from operating it...... 3yrs later and they had to hire a guy just to get it running properly.

He doesn't allow any input from us shop guys.... He says do this and walks away.... When we encounter a conflict he's nowhere to be found. He tells us to weld something solid.... Comes back and says nvm cut it off.

When we encounter a problem, we diagnose the root of the problem and work from there.... Divide and conquer.

He comes over and starts making adjustment after adjustment without time to see if it fixed it. He tells us to change this, that, this and those. He may have us change every chain on the machine because there's a skip on one drive... But when we try and explain to him that the problem is friction or binding he says change it all.

The problem still exists and he says ohh... The binding...

Yep

Engineer, Installer, Tech.... Not always the same thing. We had all three. But IF the installer did it to the Engineer's spec and was fubar, that usually was the Tech's job to fix it... At that point, I traveled back up the ladder to the top. If the installer was clear, then eng. was next to get crapped on... I was an electronic tech and out of all the engineers I met, there was only one I met that could talk turkey on the same level and vice versa.

 

And you know why this happens all too often? Because the engineers refuse to talk to the guys in the field... They use their knowledge which could be sound, but they have no clue what all the after affects are outside his lab. They need to talk before design.. Hash things out and then design.

 

 

 

 

Sent from John's iPad 2 via Tapatalk HD

Typos courtesy Apple...

 

i think you almost nailed it. engineers are some farking intelligent people. smarter than i will ever be. but they have book smarts.

 

what needs to happen(in my opinion), is that engineers should HAVE to work in their chosen field in the field for at least a year, fixing messed up designs. then they can go do their engineering thing.

Not all of us engineers are limited to book smarts fellas... Sure, I have the pedigree from a few fine academic institutions, BUT I worked in the family construction business, sawmill, machine shop, and also built and raced everything with wheels! Many classic engineers are like me, and while I hear you techs you don't factor in the changes that occur downstream of the original design that result in design revisions. Once upon a time, engineers designed for indefinite life - I could give you many examples right in the Delaware Valley - however, we now design everything with a finite design life. For the record, I manage an engineering staff of 37 currently in my division that span from licensed professional engineers through trained technicians. I will absolutely guarantee you that there is nothing one of my technicians know that I do not or any of my design engineers, and no matter who discovers an issue, better way, gotcha - it is shared among the ranks. Difference is, I do not work in the realm of mass-produced at cheapest cost for most profit items where if you understand the process of how the end product is ultimately derived, you really wouldn't be blaming the engineers...

Not all of us engineers are limited to book smarts fellas... Sure, I have the pedigree from a few fine academic institutions, BUT I worked in the family construction business, sawmill, machine shop, and also built and raced everything with wheels! Many classic engineers are like me, and while I hear you techs you don't factor in the changes that occur downstream of the original design that result in design revisions. Once upon a time, engineers designed for indefinite life - I could give you many examples right in the Delaware Valley - however, we now design everything with a finite design life. For the record, I manage an engineering staff of 37 currently in my division that span from licensed professional engineers through trained technicians. I will absolutely guarantee you that there is nothing one of my technicians know that I do not or any of my design engineers, and no matter who discovers an issue, better way, gotcha - it is shared among the ranks. Difference is, I do not work in the realm of mass-produced at cheapest cost for most profit items where if you understand the process of how the end product is ultimately derived, you really wouldn't be blaming the engineers...

 

That's the type of engineering firm that gets stuff done. At mine job that would only be a dream. Engineers like myself who have hands on understanding and are put in the field at times get drown out by upper management who decides the concerns of us and the assemblers is unneeded.

Not all of us engineers are limited to book smarts fellas... Sure, I have the pedigree from a few fine academic institutions, BUT I worked in the family construction business, sawmill, machine shop, and also built and raced everything with wheels! Many classic engineers are like me, and while I hear you techs you don't factor in the changes that occur downstream of the original design that result in design revisions. Once upon a time, engineers designed for indefinite life - I could give you many examples right in the Delaware Valley - however, we now design everything with a finite design life. For the record, I manage an engineering staff of 37 currently in my division that span from licensed professional engineers through trained technicians. I will absolutely guarantee you that there is nothing one of my technicians know that I do not or any of my design engineers, and no matter who discovers an issue, better way, gotcha - it is shared among the ranks. Difference is, I do not work in the realm of mass-produced at cheapest cost for most profit items where if you understand the process of how the end product is ultimately derived, you really wouldn't be blaming the engineers...

 

I'm going to have to come up for a cup of coffee...

If you are lucky to work for a company with that mind set, that's great. Pretty sad... but most of the engineers I can only imagine are straight out of school. Out of everyone in my office, there were only a couple techs with diplomas in anything. I was one of them. Most of our management new nothing. The engineer I worked with was as you described. Reason why we both got along with each other. Hell, most of my guys didn't even understand the resistor color code other than what few resistors they needed in the field. I just wish there were more engineers that were seasoned from the bottom up. Same with techs too...

 

Not all of us engineers are limited to book smarts fellas... Sure, I have the pedigree from a few fine academic institutions, BUT I worked in the family construction business, sawmill, machine shop, and also built and raced everything with wheels! Many classic engineers are like me, and while I hear you techs you don't factor in the changes that occur downstream of the original design that result in design revisions. Once upon a time, engineers designed for indefinite life - I could give you many examples right in the Delaware Valley - however, we now design everything with a finite design life. For the record, I manage an engineering staff of 37 currently in my division that span from licensed professional engineers through trained technicians. I will absolutely guarantee you that there is nothing one of my technicians know that I do not or any of my design engineers, and no matter who discovers an issue, better way, gotcha - it is shared among the ranks. Difference is, I do not work in the realm of mass-produced at cheapest cost for most profit items where if you understand the process of how the end product is ultimately derived, you really wouldn't be blaming the engineers...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.