Hacker News new | past | comments | ask | show | jobs | submit login

There's another thing about your comment. I suggest you reflect on this:

If you believe that someone who solves fizzbuzz in an idiosyncratic way would also do everything at work in an idiosyncratic way, you are essentially supporting the value of asking programmers to solve programming problems in job interviews.

I have a different belief. I have written a blog post on the subject, but the TL;DR is that the purpose of this kind of test is strictly to get rid of impostors whoc an't do any programming whatsoever.

The moment you are convinced that they are not a complete no-hoper, you can stop the test and get on with teh real interview.

As such, I believe it is harmful to take anything other than a single bit of information from it: Can/Can't.

If you actually study how they got it to work, and make extrapolations about them from it, you are incentivizing people to write millions of units tests, ask you whether there is a roadmap for future changes, set up a repo on github and submit their solution as a PR, &c. &c.

If that's what you want to know about a candidate, fizzbuzz is a ridiculously inadequate test.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: