trying to find a good desk jockey who didnt crash tools and wreck parts every hour.
Semi-side story: In college I had to take a CNC course as part of my minor. We were given a drawing of a part to be produced on a CNC lathe as our final class project.
It was generally assumed we were to generate the coordinate list by hand. It was a lot of grunt work so I wrote a Pascal program on the side to compute the delta's, do some basic range checking, and draw a rough plot via "ASCII art". I only had to enter the raw coordinates. Using this program I got the delta list done and and it all checked out in theory and I thought I was a real hot-shot.
Then came time to actually machine it. A teacher's assistant inserted a raw aluminum block, loaded my punched tape, closed the transparent lid, and pressed "Go".
The CNC lathe started shaping the part according to plan. I started smiling as it got near the finish, for the part forming before my eyes looked just like the assignment drawing.
Then suddenly aluminum started spraying out like crazy from the cutting tool, making a sharp jarring "neeeaaarrr" sound. Internally I thought "Oh shit!" Mentally, that was my grade being shredded before us.
Soon the horrible noise ceased, and the machine completed the action. There was a little rough patch near the end, but otherwise the part visually looked good.
Not knowing what to think, I glanced at the teacher's assistant. In a monotone voice, he said, "You had some excessive delta's, but otherwise the shape is correct. You get a B- on it. You almost broke the blade. If the blade had broke, you'd get a C-. You got lucky". (They were used to broken blades for students.)
Turns out my Pascal delta distance checker only checked the "x" distance due to a bug, not the Pythagorean distance.
Had I done it all by hand, I'd probably avoid or catch that mistake because I'd be "experiencing" the direct data details. Automation is not always a free lunch.
(Arguably I could have also spent more time checking the software, but that could take approximately as long as hand computations.)