|
|
|
|
|
|
by creature
4671 days ago
|
|
|
I think you're being overly generous here by calling it 'fluff'. I'd call it 'lies'. I'm like you. A couple of months ago I screened a candidate who listed 'Object-oriented Javascript' in second place on his list of skills. I asked him a really tough, brutal question to test this limits of his knowledge on this: "How do you do object orientation in JavaScript?" Blank look. Silence. Okay, let's help him out: "Well, JavaScript doesn't give you a 'class' keyword or an 'inherits' keyword. So how would we write OO code?" "... To be honest, I've only ever done it in jQuery." he said. "Oh right, okay. I've never done it in jQuery. How does it work in jQuery?" I asked. Silence again. No hire. I have no idea why people expect this stuff to pay off. It wasn't a front-end job; OO JS wasn't a job requirement and wasn't listed on the job ad. Why put it so high up on your CV if you don't know anything about it? Why put it on there at all? |
|
|
Like Scrum. I've worked in Scrum, and I love it. But I didn't really consider it a skill until recruiters pointed out that clients wanted clear Scrum experience.
I've listed SOAP. Is it a skill? It's fairly trivial to work with. (Though I'm amazed some people manage to mess it up. Tools do everything for you. How do you mess that up? But somehow they do.) But I've got experience with it, so I list it, though I'm hardly a SOAP guru.
I don't list Linux, because I'm no system admin. I do know my way around the command line, but everybody programmer can do that, right? Right?
So I've got some skills listed that I consider fluff, but they're not lies. I consider them fluff because they don't really add much, and are certainly not on the same level as a language or framework, but I list them anyway because hiring managers care about them.