Live data from Hacker News

Codefights

codefights.com

51–60 of 86 posts

Re: Codefights

#51

Maybe I'm just showing my low IQ, but it takes me 20 or 30 seconds just to understand some of the problems. Maybe introduce difficulty levels? Currently, I can't ever solve a problem if it takes me more than 1 minute - I'd like to be able to get to an answer, even if it's then worth zero points (or even goes into negative points?). I like the idea, but I can't play more than 2 or 3 rounds. Or maybe the game just isn'…

I think the font size has something to do with it. Maybe the description should be in bigger font outside the code block?

Re: Codefights

#52
/ * @Input1: an array of strings * @Input2: a separator that will be used when concatinating * the strings from @Input1 * @Output: a concatinated string * @Example: myConcat(["Code","Fight","On","!"],"/")="Code/Fight/On/!/" */

Guess s/concatinated/concatenated/g wasn't the bug...

Re: Codefights

#53

One suggestion for the founders, don't start the timer until the code has loaded, and stop the timer once you submit. I lost 10-15 seconds to loading the code and then got game over because i submitted with 10 seconds left and it took longer than that to actually send.

Let's see how quickly they can fix that bug...

Re: Codefights

#55
post #44

I think you should show the comments first without a time-limit and then allow the user to play. For example: /* * @Input1: an integer * @Input2: an integer (@Input1 Right now it takes me 20-30 seconds just to read and understand the comments.

Why should reading the code be timed, but reading comments not timed?

Re: Codefights

#58
post #44

I think you should show the comments first without a time-limit and then allow the user to play. For example: /* * @Input1: an integer * @Input2: an integer (@Input1 Right now it takes me 20-30 seconds just to read and understand the comments.

Why should reading the code be timed, but reading comments not timed?

Reading the comments is about understanding what the function is supposed to be doing. Reading the code is about actually finding the bug. I can see the argument for allowing one to understand the problem prior to hunting down the bug.

Re: Codefights

#59
post #58

Earlier quoted context omitted.

Why should reading the code be timed, but reading comments not timed?

Reading the comments is about understanding what the function is supposed to be doing. Reading the code is about actually finding the bug. I can see the argument for allowing one to understand the problem prior to hunting down the bug.

While I understand point people are making, I think understanding the problem is part of the debugging process, and should be a part of the puzzle and timer.

I remember entering programming competitions in high school and college. The first 5 minutes, when everyone is ripping open the envelope of their problem packet and trying to find the easiest problems was always very intense, and fun! Sometimes you would read through it too quickly, and miss a small detail that would render all the code you wrote completely useless. That's part of the challenge!

Re: Codefights

#60
post #44

I think you should show the comments first without a time-limit and then allow the user to play. For example: /* * @Input1: an integer * @Input2: an integer (@Input1 Right now it takes me 20-30 seconds just to read and understand the comments.

Why should reading the code be timed, but reading comments not timed?

Because this is a test of ones ability to code; not the speed at which they can read English.

As I said earlier: https://news.ycombinator.com/item?id=8207116

Post reply on HN