Why wouldn’t I give an honest answer? A dishonest answer is going to make me miserable. Most of the processes my company makes we make so much that we can give good estimates on total yearly cost. It would be easier for me to just hand over that data vs making up new fraudulent data that could survive a court challenge. As Mark Twain mentioned, if you tell the truth you don’t have to remember a damn thing. Besides they would easily be able to point to the numbers going over budget and demand free parts or free service.
Your idea about having your own people is why I yelled in my other comment. Those people are the worst. The more my customer understands the more problems their system will have. I know one horse towns in deliverance country using systems that smash the recommended operating lifespan and I know places that have all this local talent who are down monthly.
Doctors make the worse patients, lawyers make the worse plaintiffs, and inhouse engineers make the worse clients. The more the design is tampered with the less likely it will work right. Don’t believe me? Go ahead and open up your chest cavity and start poking around, maybe try to get your kidneys to work faster. That is what it is like dealing with the local engineering “talent”. They are overconfident, weight in on stuff that they don’t understand, follow ancient specs, and pretty much every other sin of engineering you can list.
Put another way. If me and my coworkers are working on process X all day every working day with hundreds of sites do you think we may know more than a person who deals with a single instance of the process? Phoenix Arizona is another great example. They have the most bottom of the barrel catty in-house engineering team of any city in the US. Kinda people who measure the paint thickness on a motor with calibers, demand a repainting if it is off by a milimeter, then leave it in direct sun, and are shocked when the motor overheats.
Why wouldn’t I give an honest answer? A dishonest answer is going to make me miserable. Most of the processes my company makes we make so much that we can give good estimates on total yearly cost. It would be easier for me to just hand over that data vs making up new fraudulent data that could survive a court challenge. As Mark Twain mentioned, if you tell the truth you don’t have to remember a damn thing. Besides they would easily be able to point to the numbers going over budget and demand free parts or free service.
Your idea about having your own people is why I yelled in my other comment. Those people are the worst. The more my customer understands the more problems their system will have. I know one horse towns in deliverance country using systems that smash the recommended operating lifespan and I know places that have all this local talent who are down monthly.
Doctors make the worse patients, lawyers make the worse plaintiffs, and inhouse engineers make the worse clients. The more the design is tampered with the less likely it will work right. Don’t believe me? Go ahead and open up your chest cavity and start poking around, maybe try to get your kidneys to work faster. That is what it is like dealing with the local engineering “talent”. They are overconfident, weight in on stuff that they don’t understand, follow ancient specs, and pretty much every other sin of engineering you can list.
Put another way. If me and my coworkers are working on process X all day every working day with hundreds of sites do you think we may know more than a person who deals with a single instance of the process? Phoenix Arizona is another great example. They have the most bottom of the barrel catty in-house engineering team of any city in the US. Kinda people who measure the paint thickness on a motor with calibers, demand a repainting if it is off by a milimeter, then leave it in direct sun, and are shocked when the motor overheats.