PUBLIC MARKS from night.kame with tag ruby

Le blogueur.

My attitude is if I'm a good Ruby programmer, and you're trying to hire me when the supply for Ruby programmers is low and demand is high, that before you even talk to me you've spent at least 10 minutes Googling for my name, looking at my code, and figuring out who I am, rather than spending an hour subjecting me to a series of ad hoc programming questions in areas I may or may not specialize in. That 10 minutes of Google will tell you a lot more than asking me to come in and scribble stuff on a whiteboard.

Le commentateur.

I take your point about the interviewer asking appropriate questions for the interview. But it sounds to me like you're telling me your skills as a coder don't extend to making your ideas and plans understood without handing someone actual finished Ruby code, written on a laptop. If that's the case, then I can't work with you.

Je suis plutôt de l'avis du commentateur : quand on embauche un développeur, ça n'est pas pour travailler avec un sociopathe qui ne voit la vérité que dans son code. En même temps, c'est un Rubyiste, donc c'était à craindre.

"I also believe the vendors’ development speed was handicapped from using C, prompting them to keep their stackup syntax simple to parse." Encore un qui n'a jamais développé en C, qui ne sait pas qu'on peut générer très facilement des lexeurs et des parseurs, et qui tente de nous faire ingurgiter Ruby de force...