Re:I have no side code projects to show you
by exodust on Thursday October 26, 2017 @04:32AM
(#15557268)
Speaking of FizzBuzz, I had never heard of the fizzbuzz test until recently in interview. In 15 years of frontend work I've never needed to find if a number is divisible by another number, so I forgot about the modulus operator '%', and stumbled on that question. Apparently not knowing about that made me unqualified for the job, above all other evidence of my frontend work and achievements. It takes less than 10 seconds to find the solution, but in interviews we are expected to have the entire JS reference guide in memory.
[ Parent
| on HN ]
Re:I have no side code projects to show you
by Thiez on Thursday October 26, 2017 @08:49AM
(#15558330)
There are plenty of ways to write fizzbuzz without the modulus operator, although it is the most obvious way. But you can also combine infinite streams, or keep track of the index of the next "fizz" and "buzz" with simple addition...
Re:I have no side code projects to show you
by exodust on Friday October 27, 2017 @01:36AM
(#15565956)
Perhaps there are plenty of ways, but finding the remainder of the division is what's needed and in my case the test was pen and paper, with just a small space for the answer and no way to test my code.
It's all good, it wasn't the role for me, I'm more creative dev than programmer and I didn't get a good impression of the company anyway. I've moved on.
Re:I have no side code projects to show you
by rzykov on Thursday October 26, 2017 @05:15AM
(#15557430)
Maybe it's better to provide access to Google on the interview. What do you think?
Re:I have no side code projects to show you
by exodust on Thursday October 26, 2017 @07:34AM
(#15557968)
Or at least the JS reference. Or design the questions to fit the role. If it's a frontend role, then ask frontend questions, not some bullshit high school arithmetic.
I wrote most of the 'fizzbuzz' function but couldn't remember the "%" operator. Tests are annoying because it's not how developers work, at least I don't work that way, without any way to verify syntax or look anything up.
I recall an interview from years ago where I was asked to show the code behind my websites and step through it explaining what it did and why I did it. This is better than a test, because you're explaining how the code works and also showing off your work.