That reminds me of a collage who applied at a company that wanted to know how many keystrokes per minute he did on average. He didn't want the job, because rewarding quantity over quality of code is a red flag.
That said, LoC is a valuable metric, but it's even more important to measure the quality (usually in 100% / WTFs per minute).
That reminds me of a collage who applied at a company that wanted to know how many keystrokes per minute he did on average
Every single ace developer I know would have aced that test, including me. Measuring keystrokes is actually a better idea than asking the candidate to find the pivot value for some QuickSort set ... :D
However, I see your point ...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That reminds me of a collage who applied at a company that wanted to know how many keystrokes per minute he did on average. He didn't want the job, because rewarding quantity over quality of code is a red flag.
That said, LoC is a valuable metric, but it's even more important to measure the quality (usually in 100% / WTFs per minute).
Every single ace developer I know would have aced that test, including me. Measuring keystrokes is actually a better idea than asking the candidate to find the pivot value for some QuickSort set ... :D
However, I see your point ...