|
|
|
What? You think just anyone can type '<' and '>'. That takes a professional!
--------------
TTFN - Kent
|
|
|
|
|
They're not really skills; more a list of languages and technologies that someone thinks might be in demand by employers. A few of them go together; for instance a web developer would need to know a reasonable mix of some of the items on the list to be able to get a job. Silly, really; single language skills are very limiting and just because you know n languages doesn't mean you're going to be any good at creating something useful with them.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
At previous jobs, they have asked me if I have "XML experience".
Having written XSLT user controls (and transforms for XML config files), SOAP web services, AJAX in various incarnations (with usually zero exposure to actual XML), HTML (and DOM composition/traversal, which is a bit like virtual XML), web.config files and other XML formats, yet calling XML a skill still has pretty much no meaning to me. It's like listing "Text" as a skill. It's just a basic file format (or a data format, as sometimes it's not actually stored in files); I doubt those asking for the skill know anything about it beyond the buzzwords (e.g., "semantic", "human readable", "web friendly", and so on).
|
|
|
|
|
Definitely agree with you, but remember where this came from; it's driven off of job ads posted. We all know who is most likely to write those posts. So, I think your last line:
AspDotNetDev wrote: I doubt those asking for the skill know anything about it beyond the buzzwords (e.g., "semantic", "human readable", "web friendly", and so on).
is completely accurate. I'm surprised that "must own car" wasn't on the list of programming skills.
--------------
TTFN - Kent
|
|
|
|