Engineerj22
Member
Thankfully at this point most of the repeat service calls I go to, the people there don't blame the program changing anymore.
As an aside, EVERY time something goes wrong in a process, it's always "The Program". The program that has been running flawlessly just mere seconds ago. NO ONE seems to understand that a program doesn't change, except programmers...Hmmm.
When things go awry, people tend to place the blame on that which they understand the least.EVERY time something goes wrong in a process, it's always "The Program".
If I'm trying to impress an attractive young lady, I'm in the environmental and energy conservation business.
If I want to be left alone, I'm in sewage.
The program doesn't change, but every once in a while I find that the program was wrong all along and just happened to produce the right results 99% of the time.
I once commissioned a system where, in hindsight, there was a tiny flaw in my communications structure. Basically, if there was a network failure that occurred after the PLC had completed executing one rung of code, but before it finished executing the next rung, it would fail to start communicating again once the network was restored. You'd think that with a relatively rare trigger like that (network failure), and such a minute window of time (we must be talking microseconds), that it would probably never happen.That "What If" you didn't think of finally happen. So true.
I don't see how you kill people's jobs. I can't see what you automate being done manually.I say: I automate industrial machinery. Like JaxGTO, How it's made often comes up. Some people will say, oh, you kill peoples jobs. Basically