Skip to content

Comment on You Can't JavaScript Under Pressure

Comments

What's everyone's times? I did 7 minutes

8: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!).

8: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.

14 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.

My JS is somewhat rusty, glad I had a .map() to work with. 9 minutes something, I did 'cheat' by looking up some typeof returns.

6:11.

Blew through the first 4 but spent half my time on the last one because I don't have Javascript type checking memorized.

"2 minutes, 32 seconds for all 5 levels. Well done!"

The "kill screen" song is stuck in my head now.

I only did one time: 8 minutes and 57 seconds, for sure the next try will be way easier.

5 minutes, 31 seconds for all 5 levels. Well done!

4 minutes, 56 seconds for all 5 levels. Well done!

11 minutes 14 seconds. I wish I did faster!

17 minutes, 47 seconds. slow poke here.

26 Minutes. If you're a slowpoke, I'm a Slowbro.

Just under 3 minutes!

12:45

2:26.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.