I would say that a lot depends on what he is promoting himself to be. A lot also depends on what qualities he was "really" expected to provide.
If he is supposed to be a "hit the ground running" programmer... lose him! He has no sense of system nor of PLC inherent capabilities.
If he is expected to be a raw-rookie, then teach him.
As weird as it might sound, when I interview a prospective programmer, after all the chit-chat stuff, the first three questions I ask are as follows...
1. Can you draw a square? Show me.
2. Can you draw a 3-dimensional square? Show me.
3. Can you develop an Off-Timer using only an On-Timer? Show me.
Everyone can do the first.
I was surprised to see how many couldn't do the second. I wasn't asking for artistic capabilities but rather "spacial acuity". This is critical to multi-dimensional motion control. Along with his "A, B, C's" one has to know his "X, Y, Z's".
I wasn't too surprised about the third. Many so-called programmers just couldn't relate to the idea of developing an off-delay effect without relying on a specifically designed off-delay instruction. That shows a lack of imagination. And imagination is "everything" in PLC programming!
Harryting said...
"Real people can get killed, whether your program runs or not."
That is the bottom line. You have to "feel in your bones" that this guy "has it".
Most, and I mean most, programmers are "hackers". Can you afford to have a "hacker" developing your process?
Using a Stop-Watch to measure event-time on a status screen? GET REAL!