5 ms·
The problem there will be that the competent engineers - if they have any - will have been burned by too many dud candidates wasting their time, and have gotten
by gaius 16y ago
The problem there will be that the competent engineers - if they have any - will have been burned by too many dud candidates wasting their time, and have gotten HR to pre-screen the CVs...
- rdtsc 16y agoThe job of a good HR department is to at least be able to screen the really dumb ones and pass the rest up the technical chain for evaluation. The good engineers might be burned out but if they know that not spending time interviewing and reviewing resumes will result in having to deal with a dud that gets hired, having to babysit them, teach them the basics of programming and watch them slowly destroy the code base, they would be quite happy to assist with evaluations.
- bugsy 16y agoIf anyone in HR had the capabilities to tell the difference between a qualified candidate and one who is lying, then that HR person is also qualified to transfer to engineering and start coding.
- eru 16y agoNot all people who can code, enjoy doing it as part of their main job.
- wglb 16y agoIn my long career, I have yet to meet anyone with a title anywhere in the neighborhood of "HR" with the ability to tell the difference.
- Unosolo 16y agoAs I see it the job of a good HR department is: 1) Make sure that job ad reaches people who are likely to be good candidates. 2) Job ad is attractive enough so that good candidates will actually apply. 3) Handle the administrative side of the recruitment process: paperwork, visas, appointments, expenses, tickets, re-location, contract, security checks etc. 4) Make sure the whole process complies with the legislation. 5) Streamline and expedit the whole thing from the very start to finish. In my eyes HR is not qualified to make a judgement if a candidate is any good at programming.
- rbanffy 16y agoI think we, engineers, can help HR folks ask important questions that would prevent bad candidates from wasting our time as well as thinking up crazy ideas that could help lure good candidates. Yesterday, I suggested going EA-style and hand out laptop stickers on an upcoming hacker-ish convention with things like ''.join([chr(c) for c in [119, 101, 39, 114, 101, 32, 104, 105, 114, 105, 110, 103]]) and (dolist (x (mapcar #'code-char '(119 101 39 114 101 32 104 105 114 105 110 103))) (princ x)) I am somewhat unsure about the Lisp thing, so I asked it to be passed through a real lisper before hitting the printer.
- Natsu 16y agoSeems like we're seeing less of perl -e "@w = (119, 101, 39, 114, 101, 32, 104, 105, 114, 105, 110, 103); foreach $c (@w) {print chr $c;}" these days.
- rbanffy 16y agoIndeed. I don't think we have any actively maintained code written in Perl. I know a lot of plumbing written in it, but it's not in need of new features.
- Natsu 16y agoSounds like it was written by a good Perl hacker if it still just works and nobody has needed to maintain it after all this time.
- chromatic 16y agoHopefully that's because a good Perl hacker would write: perl -E 'say map { chr } 119, 101, 39, 114, 101, 32, 104, 105, 114, 105, 110, 103'
- Natsu 16y agoperl -e "print map {chr} 119, 101, 39, 114, 101, 32, 104, 105, 114, 105, 110, 103;" is the best my version can do. I still need to read more of that book of yours. And update my install: neither say nor -E exist.