NOTE: Wearing my 'I am a Java Programmer' Hat (not my mod hat)
Having spent some time recently on Code Hunt, I would actively recommend that people avoid it:
Stay Away! This will teach you the wrong things!
Code Hunt is unlike other 'challenge' sites I am familiar with, in the sense that it is more about identifying the problem, rather than identifying the solution.
It gives you a 'truth table': the provided inputs, and the expected outputs. Your job is to convert the inputs, to the outputs. To do that, you have to build a 'black box' of code that does the transformation. If your black box meets some criteria, it scores highly.
After the first few (tutorial) 'challenges', you need to 'hunt' for what to put in the black box. If your 'guess' is wrong, you get some additional information (a new input/output line on the truth-table). You need to identify what the 'algorithm' is to do the transformation.
It is a 'trial and error' system. It encourages you to try things without basing your attempts on a problem statement. You have to guess the problem before you can guess the code.
In addition to the above, the scoring system appears to favour bad code-practices. Slow and inefficient 1-liners have been shown to score high, whereas fast and efficient solutions (10 times faster) have scored poorly, just because they took 3 lines.
So, you have to:
- guess the problem
- guess the solution
- guess what ugly mess you have to make so that your efficient/readable code can be transformed in to golfed crud, in order to score high...
In all, while I think many code-challenge sites are good, the Code Hack site is a bad concept.
Also, it should be noted that it is likely a recruitment tool for Microsoft Research.... and, it worries me (or is it 'the penny dropped' AHA!) that Microsoft Research values obscure, slow, 1-liner solutions to problems they 'invent' and 'solve' with inefficient code.
Now, wearing my Mod hat, (and the Java hat)
Simon accused me of not answering the question: how we should review Code Hunt related questions?
Standard Code Review answer is:
Can you describe the problem you have already solved? Does the code work?
- for Code hunt, this means you need to have determined what the algorithm is, and probably got at least 1 out of 3 already
- you have code that produces the right results.
- you have described the problem, not just "given the inputs a, b, and c, produce the values x, y and z")
Is the question about: Do I want the code to be good code, (i.e. not code-golfing, obfuscation, or similar)
- I want the code to be good code, not just code that scores 3 out of 3.
If the answer is yes, then sure, the question is a good one for Code Review