5 ms·
What's everyone's times? I did 7 minutes
by ep103 13y ago
What's everyone's times? I did 7 minutes
- Justin_Time 13y ago4 minutes, 56 seconds for all 5 levels. Well done!
- mneary 13y agoJust under 3 minutes!
- hatsuseno 13y agoMy JS is somewhat rusty, glad I had a .map() to work with. 9 minutes something, I did 'cheat' by looking up some typeof returns.
- CompelTechnic 13y ago17 minutes, 47 seconds. slow poke here.
- dclowd9901 13y ago26 Minutes. If you're a slowpoke, I'm a Slowbro.
- robflynn 13y ago"2 minutes, 32 seconds for all 5 levels. Well done!" The "kill screen" song is stuck in my head now.
- trevordixon 13y ago4:20.
- renekooi 13y ago2:26.
- methodover 13y ago14 minutes, 27 seconds for all 5 levels. Bah, should've done better. On the other hand I just woke up. I wanna see one of these in Python.
- Demiurge 13y ago12:45
- ryanthejuggler 13y ago3:15
- nakovet 13y agoI only did one time: 8 minutes and 57 seconds, for sure the next try will be way easier.
- dmak 13y ago11 minutes 14 seconds. I wish I did faster!
- dpedu 13y ago6:11. Blew through the first 4 but spent half my time on the last one because I don't have Javascript type checking memorized.
- myh 13y ago5 minutes, 31 seconds for all 5 levels. Well done!
- oftenwrong 13y ago8:30 Spent nearly the entire time on #3 because I was trying to use String.replace to work and failing. Ended up using .split instead, which passed thanks to poor test coverage (just like at work!).
- EdgarVerona 13y ago8:11 for me - as it sounds like was the case with others, the majority of that time was searching for how to check for specific types in Javascript. For the "is this actually a string?" check, for example, I started looking for the existence of the match method on the object, which of course would have failed if they passed some random object with match defined so I cheated a bit. I'd like to see the full breadth of test options people took out there.