To view parent comment, click here.
To read all comments associated with this story, please click here.
Why are you so shy to explain what's wrong? Seriously, if you would be a teacher, as you try to impose now, you'd be a really bad one.
So let's accept there is a bug depending on integral representation.
The other bug of course is _your_ use of "int", apart from other issues.
---
About the confidentiality: Seriously, I don't know how you define it in your company. But that code is indeed something personal, as are his answers or his resume. Additionally, you've screwed that guy before the others, and possibly no one who opens his/her own company will now ever hire him, or upon changing the job give a recommendation to the boss.
I don't know. The mills of data are patient.
It boils down to: What business do non-HR ppl have with documents from closed-room-interviews? Why use the illusion of a closed room at all (I assume that by the timeline you imply)? Well, let me break your illusion of you being "better".
I'd really like to ask which company that is you work at, so I can put it onto my "never waste money/time on that" blacklist, neither job-wise, nor business-wise.
Edited 2012-09-25 14:00 UTC
The problem is how do you treat number that consist of 1 followed by a bunch of zeros. So, when he is talking about a bug, he probably wants to treat return value as unsigned int.
I can't see any other problem with the code.




Member since:
2010-06-12
That bug is your homework. Test the code thoroughly, and you'll find it very quickly.
Confidentiality only applies to personal information and all the documents sent to me or to the company. It doesn't apply to codes written by anyone during the interview. I haven't disclosed any bit of personal information pertaining to that guy, now have I?