hexagon logo

Power Trip

You know, I have seen more often, People on here going to great lengths and just, extra steps, on writing programs to keep others out of PC-DMIS and the programs. I think if you spent that effort teaching others, how it works, how it functions. Lets face it, the CMM is an instrument used for quality, If a person is in quality, do we hide Calipers, OD, ID mics, indicators, surface plates, blocks. I know there are people out there, who might think, That their job is threatened. Paranoid.Alien Then there are others who say, that's what the customer request, my hands are tied. Your customers are not at your place all the time, nor are you, what happens when something goes wrong, are you going to end your vacation and head back to fix it? are the customers going to come over and fix it? Last but not least, The power trip people, They have in their feeble little heads "I'm GOD, You will bow down to me and worship me, My intelligent level is superior to yours" The only thing I can say to those people is "S-h-i-t and fall back in it" Just my 2 cents for the day Rolling eyes

This is what got me saying what I said. I always said there are no dumb questions, just dumb answers. Well I might have to revisit that saying.

Parents
  • At one time I was deeply involved with training people. I never trained on how to calibrate the probe rack, because once it's set up there's almost never a need to do it again. If you do need to do it again, you definitely won't remember from the 30 minutes spent on it during a training session a few years previous, particularly when that training session was overwhelming with new learnings to begin with. It's like the ellipse auto feature - why teach it? There are virtually no true elliptical forms out there (usually specific industries), it's worthless knowledge for the vast majority of people out there.
  • The thing is that you need both button pushers and programmers. Potential Programmers are much harder to identify and develop. I don't have a problem giving programmer trainees full access to the program as long as they discuss their changes with me. When they are first starting out I want to see every thing that they are up to so that I can provide feedback. As time goes on, I expect that I expect to be reviewing changes less and less. This is a whole different thing then letting anyone and everyone make wholesale changes to programs. Again, not an ego thing, but common sense.
Reply
  • The thing is that you need both button pushers and programmers. Potential Programmers are much harder to identify and develop. I don't have a problem giving programmer trainees full access to the program as long as they discuss their changes with me. When they are first starting out I want to see every thing that they are up to so that I can provide feedback. As time goes on, I expect that I expect to be reviewing changes less and less. This is a whole different thing then letting anyone and everyone make wholesale changes to programs. Again, not an ego thing, but common sense.
Children
No Data