3 ms·
Try asking them. "Hey, do you find most of your colleagues are familiar with your code or do you find most of them have trouble getting up to speed with it?" Y
by raganwald 18y ago
Try asking them.
"Hey, do you find most of your colleagues are familiar with your code or do you find most of them have trouble getting up to speed with it?" You can ask this question in a very neutral tone, one that implies that the colleagues may have been at fault.
And then, be very careful to determine whether the colleagues really weren't at fault. If you're trying to hire a very smart person, you may find someone who has chafed writing J2EE code in BigCo, and yes his code was inscrutable to his colleagues, that's why he wants to write Python code for you.
- stcredzero 18y agoI've witnessed solo programmers writing brilliant but inscrutable code in Smalltalk. Bittorrent's code also fit this description for awhile. Someone who writes inscrutable code in J2EE in BigCo might do so because he's hobbled by their coding standards. But he might be one of those folks who is a brilliant coder but has no sense of what is intention revealing to those reading his code.
- raganwald 18y agoI agree. All I can say is... the OP mentions indicators. It is absolutely correct that they are merely hints. You still have to interview them and/or test them and/or check references from former employers and/or check references from former colleagues, and/or... In this particular case I speak as someone who has received both praise for my ability to write code that my colleages find crystal clear and vilification for writing code that my colleagues find inscrutible. Did I mention code samples? I have code I can share. I like it when I'm interviewing and someone has code they can share.