I think I'm fairly fast at debugging but these were way, way too hard with the strict time limit. It takes a lot of time to read the problems and the quality of the problems is poor.
Codefights
61–70 of 86 posts
Re: Codefights
#62I love the idea. It still needs more problems though. I kept hitting the regEx problem and failing because I've never done regEx in JavaScript. So adding more problems would be nice.
Re: Codefights
#63Great to see CodeFights being launched! I enjoyed the graphics and dynamics of MathFights.com as well, well done, Tigran and the team.
Re: Codefights
#64Interesting idea.
Several of the solutions I encountered are just... plain done wrong. They have a bug, sure, but the bug's actually there cause it was written in a really hacky way instead of the simplest way that would implement the function.
I feel like it took me longer to find the bug in the hacky implementation than it would have to rewrite it 'right'.
(For instance, the 'right' way to find "largest integer with x number of digits" is clearly and inarguably `Math.pow(10, x) - 1`. Not the hacky 4-line-with-for-loop thing they showed me with a bug in it. No?)
I wonder if it would be interesting to have something like this run your solution through a simple test suite to see if it works (like my university professors used to do on our homework), instead of accepting only one exact right answer.
Re: Codefights
#65Interesting idea. Several of the solutions I encountered are just... plain done wrong. They have a bug, sure, but the bug's actually there cause it was written in a really hacky way instead of the simplest way that would implement the function. I feel like it took me longer to find the bug in the hacky implementation than it would have to rewrite it 'right'. (For instance, the 'right' way to find "largest integer wit…
This reminds me of more than one job interview I've had. One included a puzzler that was "fix this horribly convoluted javascript code by adding exactly four characters." I'd consider myself a pretty good bug finder-and-fixer. As in, I've read multiple books on debugging methods and even given some talks on effective debugging. Nevertheless, these kinds of stumpers make me freeze up.
I dunno exactly what puzzles like these demonstrate. That you spend a lot of time working in poorly written code?
Re: Codefights
#66After I fail a challenge, the screen disappears too quickly for me to continue looking at the challenge and figure out the correct solution. Is there a way to enable feedback or solutions?
Re: Codefights
#67After I fail a challenge, the screen disappears too quickly for me to continue looking at the challenge and figure out the correct solution. Is there a way to enable feedback or solutions?
there is actually a workaround right now (not a great one but still). If you go to Forum from the top nav bar then click tasks you can see all of the tasks that you ever got during your codefights.
Re: Codefights
#68This is like a hackathon project I had this year at HackRU.
Re: Codefights
#69This is like a hackathon project I had this year at HackRU.
I am still working on mine though, who made codefights?
I would like to get in contact.
Re: Codefights
#70This is very nice. More engrossing than most games I play. Instead of starting over every time I lose, I would prefer if I was penalized and allowed to continue playing. For instance, if I lose round 5, then I will also lose all the points from round 4 and continue playing from round 4 instead. It's just something that I thought would make it more interesting and playable for me.