4 ms·

Seriously? Commenting while the sausage is being made? I'd prefer you tell me what sausage you want, then you can comment on the taste. But commenting on the w

Seriously? Commenting while the sausage is being made? I'd prefer you tell me what sausage you want, then you can comment on the taste. But commenting on the way I turn the casing machine handle to the left, rather than the standard right, is going a bit too far.

asadlionpk 13y ago
Hello, we are in a private beta and have been using it for our own use for a month now :) But I agree with you on the sausage analogy... we just wanted to see how much people sign up for the next beta so we can prepare (technically and mentally) for it.
elliottcarlson 13y ago
Yes and no - part of a coding interview shouldn't just be can they get to the answer, but how do they get to the answer. If the solution to someones FizzBuzz is simply pre-coding the answers and printing them to the screen line by line, checking that you haven't reached the X limit in the request, then yes - you made it output everything correctly, but seriously, that's not someone who I would want working for me. In this case, you should also be judging how someone makes the sausage, and how they use the casing machine. On the other hand, another part of a good interview should be the conversation surrounding the coding exercise. Seeing if someone can come up with a better solution, or even explaining their thought process. Just because they cranked the casing machine to the left doesn't mean it is wrong either. Either way you should definitely be reserving your thoughts and evaluation until the end, since people can easily make mistakes and quickly turn around and impress you.
xerophtye 13y ago
While i agree that personally as the CANDIDATE, i'd probably want to get to finish everything and THEN let them see what i did, but as someone commented what's more interesting than just the code is the analysis and thought process that led up to it, and this product seems to help analyze that better

asadlionpk 13y ago

Hello, we are in a private beta and have been using it for our own use for a month now :) But I agree with you on the sausage analogy... we just wanted to see how much people sign up for the next beta so we can prepare (technically and mentally) for it.

elliottcarlson 13y ago

Yes and no - part of a coding interview shouldn't just be can they get to the answer, but how do they get to the answer. If the solution to someones FizzBuzz is simply pre-coding the answers and printing them to the screen line by line, checking that you haven't reached the X limit in the request, then yes - you made it output everything correctly, but seriously, that's not someone who I would want working for me. In this case, you should also be judging how someone makes the sausage, and how they use the casing machine. On the other hand, another part of a good interview should be the conversation surrounding the coding exercise. Seeing if someone can come up with a better solution, or even explaining their thought process. Just because they cranked the casing machine to the left doesn't mean it is wrong either. Either way you should definitely be reserving your thoughts and evaluation until the end, since people can easily make mistakes and quickly turn around and impress you.

xerophtye 13y ago

While i agree that personally as the CANDIDATE, i'd probably want to get to finish everything and THEN let them see what i did, but as someone commented what's more interesting than just the code is the analysis and thought process that led up to it, and this product seems to help analyze that better