I think anyone that has really done that much coding wouldn't make that mistake. (If they made that mistake on a resume... they aren't detail oriented enough for me.)
I've used most of those (PeopleTools, I don't know), but I definitely wouldn't put them on a resume; because I don't think I know enough.
Is that person implying frequent use or familiarity ? Passing "I've seen what this looks like, read some code, fiddled with it" type answers are certainly possible.. Developer level, I-dont-need-no-stinking-reference-manual type knowledge.. ? umm, wow.
That's why I extend linguistical concepts to my resumé, based on my (perceived) ability to read (understand) and write (produce) some technology: fluent, literate, conversant, and familiar.
Most interviewers have commented favorably on that approach, although I have had to explain it more often than not.
I think I'm going to steal that idea. I split my skills into similar categories, they just didn't sound as impressive. I still think I need an extra category for "acronyms beginning with 'X' I call bullshit my way through", is there a proper linguistical term for that?
"Perl/CGI... PHP". Is he implying he knows "Perl/CGI", or has used Perl only for CGIs? Does he not think PHP is CGI? Is CGI just implied with saying PHP and needs to be specified with Perl?
Yeah, I'm always skeptical when too many odd combinations are listed. I think those resume sections need to be targetted for the job under consideration. If the job was such that all those Java, Perl, XML skills are listed, why bother cramming in Dreamweaver, too? I usually don't care if my programmers know MX or not.
I wouldn't hire them (Score:1)
I think anyone that has really done that much coding wouldn't make that mistake. (If they made that mistake on a resume... they aren't detail oriented enough for me.)
*shrug* (Score:1)
I've used most of those (PeopleTools, I don't know), but I definitely wouldn't put them on a resume; because I don't think I know enough.
Is that person implying frequent use or familiarity ? Passing "I've seen what this looks like, read some code, fiddled with it" type answers are certainly possible.. Developer level, I-dont-need-no-stinking-reference-manual type knowledge.. ? umm, wow.
Re:*shrug* (Score:1)
That's why I extend linguistical concepts to my resumé, based on my (perceived) ability to read (understand) and write (produce) some technology: fluent, literate, conversant, and familiar.
Most interviewers have commented favorably on that approach, although I have had to explain it more often than not.
Re:*shrug* (Score:2)
Re:*shrug* (Score:2)
Just mark that down as "fluent", just like the next guy.
I'm with phillup (Score:2)
Re:I'm with phillup (Score:2)
The real shock to me is that somebody would claim that they had working knowledge of so many disparate technologies.
Re:I'm with phillup (Score:2)