Mike, just got it, and that looks like a good catch. Will report as soon as I make the edit, which will be after this.

I was pretty freaked to find out my tech isn't exactly a tech. NOW.. let me propose something. If your main skill is in connections and knowing who knows what.. That's a viable skill. Your referrals might have much more value for the time it would take me to find and screen freelancers.

IF they'd re-name your position to "Support Liason", I still might have see more chosen you. A liason might be a better option because they could have a wider range of options to choose from. In it's single agent form, we might get an expert at dolphins template system, but weaker in PHP, or a js wizard that doesn't think of other ways to use the template system.

I wasn't bashing your skills or lack of, as much as I was reacting to the surprise of assuming one thing and finding it inaccurate.

Knowing I have a laison, rather then the hands-on coder.. I'd know to allow for extra days to track the right resource. Something I would not expect from one who can read lines on the fly.

This cron.php is a case in point. It did take a long time. But in the end, the reply comes from someone who seems pretty confident to have spotted the error quickly. So same end result, the only difference being time. I can deal with the time factor, so long as I know that it IS a factor. I think we're cool with this solution.

But you have to admit, this was akin to my Doctor saying "I really don't get how the body works, but I really like working in hospitals, and I know some awesome nurses."

Methinks your bosses have language nuance issues. Industry definitions and descriptions have to be consistent. Maybe they'll get the term Technical Embassador."