You want to know how...

[CNCAppsJames]

... you can tell a programmer isn't as good as advertised? In no particular order;

1) They fumble around. Then when asked about said fumbling the reply is "...I've run X control before and it didn't look/behave this way...".
2) When attempting to probe with a standard measurement cycle they can't even get the argument declaration correct, then proceed to say it's worked that way on every other machine they've run except this one. The machine/software gets blamed when said cycle returns MACRO alarms and they don't even have a clue as to how to troubleshoot it, and the problem shines as bright as the sun to anyone with even a VERY basic understanding of MACRO argument declaration.
3) When their parts come out with discrepencies, they blame the machine, blame the work holding, blame software bugs, blame the post, blame the machine again, blame the holders/tools, blame the tool measurement system, blame everyone AND everything but the person in the mirror.
4) They start looking at irrelevant modal commands in the display and ask "why is this on?" And when I don't know other than it may be one of the selections available when RESET is pressed, it then forces me to dig into the Parameter Manual to attempt to figure it out. Knowing full well it's completely irrelevent to thier self inflicted problems... but, I gotta do the dance because if I don't, then THAT is the problem. It's part of the gig I signed up for, and I'm cool with it because I ALWAYS walk away from parameter manual digging sessions with more knowledge than when I approached, BUT, I'm not there for me. I'm there to solve their alleged problem, which they created because they failed to heed sound, proven advise about how certain functions work in a CNC machine, and refuse to acknowledge they don't know about these things they said they knew. 
5) They proceed to tell you that Machine X worked perfectly and that this Machine Y they are trying to run isn't like any other they've ever seen with Z control on it. :sigh: 

It really sucks when supposed professionals don't own their shortcomings, and then proceed to send applications staff, service techs, and other support staff down rabbit holes.

Full Disclosure;
1) I have my hands on multiple machine builders' machines on a regular basis. I have my hands on 1st time for me machines all the time and often each different machine has a different interface so I do fumble around form time to time, so I get it.
2)I consider myself a strong intermediate with regard to command of FANUC Custom MACRO B. Math operations are probably my most singular glaring deficiency. If it were not for CAD/CAM/CAE software and Excel, and my ability to solve complex problems with those tools, I'd probably have to revert back to working on a dairy farm cleaning stalls.
3) The machine is the LAST thing I blame.
4) A misplaced G69, G54.4P0, an active G41, etc... have caused me trouble in the past, and every once in a while I'll still miss one.
5) I'm always running new machines. Probably a few a year at minimum. I'm going to ask the Manufacturer AE's advise and proceed as ifg I know nothing, and will be up front about it. I've only ever had one customer complain about "Why did you send me a rookie?" Bill reassured him that even though I was learning on the customer's equipment, they would not be disappointed at the end result.

I do not know everything. I will never profess to know everything. I may be confident in my skills, perhaps too confident from time to time, but relax, the project that is going to put that ego in check is right around the corner and I will be humbled yet again. But, I cna always fall back on I don't know everything.

[Zoffen]

the saying "give them enough rope to hang themselves" seems to fit this scenario nicely.....

[gcode]

That's one of the problems with staying at one place for a long time
You don't get the wide range of experience you'd get changing jobs every couple of years.
I haven't run a machine since 2001 and it's been that long since I wrote a macro.
Back in the day I wrote some pretty cool family of part macros for 4th axis work.
Enter the dash number of the part at the start of the file and it would machine a hex and 3
safety wire holes on any one of 24 different parts.  That's old news though, use it or loose it.
 

[JParis]

That's old news though, use it or loose it.

Yup...had it, lost it, slowly getting back now that I'm using it more and more for probing and program control and such...

Other than that very short stint at Sig(4 months), I've not touched a machine since 2004

[Tim Johnson]

That's one of the problems with staying at one place for a long time
You don't get the wide range of experience you'd get changing jobs every couple of years.
I haven't run a machine since 2001 and it's been that long since I wrote a macro.
Back in the day I wrote some pretty cool family of part macros for 4th axis work.
Enter the dash number of the part at the start of the file and it would machine a hex and 3
safety wire holes on any one of 24 different parts.  That's old news though, use it or loose it.
 

I haven't run a machine since 1988 and right now I'm writing a macro to transfer a fixture offset to the part because engineering wants a feature coming from a .025" oversized casting ±.010 from the top surface machined into the side.

[Jim at Gentex]

I haven't run a machine since 1988 and right now I'm writing a macro to transfer a fixture offset to the part because engineering wants a feature coming from a .025" oversized casting ±.010 from the top surface machined into the side.

Is giving the engineers a vigorous beating an option?   
It should be...

Seriously though, good topic.
Funny how everything is a matter of perspective.

I'm on the other end of that spectrum as I run a machine almost every day, and programming is secondary.
Sometimes I am slogging through production parts for days and weeks on end, so at times like that I feel like my programming skills are getting dull. 

When I first started this job is was mostly R&D work, probably 60/40 programming/operating.
Now the focus of our CNC Department has shifted more toward production, so the ratio is probably closer to 80/20 operating/programming.

The most exciting days for me now are when a new part, or fixture, or both come through the system and I actually have the opportunity to create some toolpaths, generate some code, and make a first piece!

I would love to do nothing but programming all day every day, but we are just not that kind of high volume shop.

I've only got about 5 more years until retirement, so I will stick it out and make the best of it! 

[neurosis]

That's old news though, use it or loose it.

When we first got our Horizontal I wrote a bunch of macros to automate some processes, run selected/multiple faces of tombstones or fixtures etc. We still use a lot of them today.

I haven't had to play with macros for a while. I went to look through one of my macros a few weeks ago and was having a hard time figuring it out. 

I think that part of that is age. I don't retain things as well as I used to. But  you're right.  You don't use it, you definitely lose it. 

[neurosis]

It really sucks when supposed professionals don't own their shortcomings, and then proceed to send applications staff, service techs, and other support staff down rabbit holes.

Not to try to compare my experiences to yours in any way, but that is one of my peeves. If you don't know something, own up to it. Don't cost hours on hours of extra time because your ego got in the way.

[DUM1]

cant seem to get on a machine unless someone cant figure something out or quits ' machine skills slipping a bit
spend more time fixing other "programmers" work more than anything
not saying my way or the hiway or anything but dam !
have one I trained a long time back and ha's a total rogue ,
hi speed tool paths for everything 
no set up sheets no levels or tool path descriptions
no view sheets , crashes tools all the time , breaks tools constantly 

he's my boss now

[Zoffen]

I haven't had to play with macros for a while. I went to look through one of my macros a few weeks ago and was having a hard time figuring it out. 

Haha yes I have this happen to me all the time, I look at something I did in the past and go "I did this?" lol

Aaaaand now I comment everything to the extreme if possible so I remember what I did a few years from now. Getting old sucks!

[Jeff]

I'm the best programmer this company has ever seen.











I'm also the only one they've ever seen. 

[YoDoug]

One time I drilled a hole in the wrong spot.

[gcode]

big fish  small pond   

[Tim Johnson]

Is giving the engineers a vigorous beating an option?   
It should be...

We have to be careful on which engineers to beat.

About a third of the mechanicals are making some damn good beer.

[Bruce Caulley]

You definitely lose it if you don't use it.  I think back to some of the more complex things I did in the past and wonder if I'd even know how to switch the machine on now