Ed, well put:
There should be no difficulty in operating with a strict procedure if the steps are specifically indicated. But it takes an organized and somewhat compulsive personality to do this. There are many who meet this requirement and many who don't.
I am an engineer, and we engineers usually work in structured,
procedural, environments, with structured, some would say compulsive colleagues. As a software designer, it's all about algorithms and step-by-step procedure.
To me, a production engineer would or should
be applying GPGIs best-understood procedures in some rigorous manner, and then over time adopt R&D improvements as they become available, also in some well-controlled way. (You've mentioned that the R&D and production may have been too commingled in the past, not good).
While this may not have been so in the past, McKay seems to be bringing good faculties to the table.
The (cynical) reference to the stock chart crossing the time axis referred to the zero-crossing (ordinate price = $0.00 at some time t); the historical chart looks like a straight line to zero!
Hopeful going forward,
hopeful that the staff gets straightened out,
hopeful that the process gets defined,
hopeful that the procedures get (iteratively) refined,
hopeful that the stock curve turns around,
hopeful that future deliveries yield better results,
hopeful that this Big Ore Pile is made to surrender it's worth.
I can't say it hasn't been interesting,
George |
