meh. Fizzbuzz is short, and you should be able to read simple code and predict its output. If you botch, catch the error, and fix it, it's a good sign. If you c

meh. Fizzbuzz is short, and you should be able to read simple code and predict its output. If you botch, catch the error, and fix it, it's a good sign. If you can't find the mistake in five lines of your own code (say, because of overconfidence...) then it's a bad sign. (I would argue that 'now, find a bug' is a good follow up question in most any coding interview, regardless of how perfect the first draft was...)