I like this idea. I find it fascinating how many developers I've interviewed who still have not come across FizzBuzz, and how many of those cannot solve the problem. Some of the more interesting interviews I've given though have been with people who know the FizzBuzz problem, where I ask them to make the worst possible version of it that they can. It turns out to be more difficult than they think it will be, and a deeper thinking and communicating exercise than solving the simple FizzBuzz problem itself.
I opened the link thinking ”hah, what a gag!” But then I thought it’d be funny to try to find the core fizzbuzz logic. Turns out that it hits way too close to home, I just got really annoyed. Not sure what I expected.
> As in most descriptions of it are annoyingly ambiguous.
My very first interviewer (intentionally) didn't spec fizzbuzz correctly. The real test was whether the candidate listened to the customer's/lead engineer's spec instead of jumping to conclusions.
Fortunately, I was just entering college and hadn't heard of fizzbuzz before. I passed the "test" but for the wrong reason.
[+] [-] ummonk|7 years ago|reply
[+] [-] bytematic|7 years ago|reply
[+] [-] codereflection|7 years ago|reply
[+] [-] jtolmar|7 years ago|reply
[+] [-] a1369209993|7 years ago|reply
Based on a true story, sadly:
On the other hand, there's also ones like: (because who needs divisibility tests, right?)[+] [-] Waterluvian|7 years ago|reply
[+] [-] octavefb|7 years ago|reply
[+] [-] Retr0spectrum|7 years ago|reply
https://mybinder.org/v2/gh/quasiben/fiftyfizzbuzzes/master?f...
[+] [-] romwell|7 years ago|reply
In the meantime, enjoy the ever-classic Fizz Buzz Enterprise Edition:
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
[+] [-] AceJohnny2|7 years ago|reply
http://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
[+] [-] toxik|7 years ago|reply
[+] [-] userbinator|7 years ago|reply
https://github.com/jongeorge1/FizzBuzzEnterpriseEdition-CSha...
[+] [-] sincerely|7 years ago|reply
[+] [-] jpindar|7 years ago|reply
[+] [-] spatten|7 years ago|reply
The code on GitHub is here: https://github.com/vihart/fiftyfizzbuzzes/blob/master/Fifty%...
[+] [-] tzs|7 years ago|reply
https://news.ycombinator.com/item?id=4922282
[1] https://en.wikipedia.org/wiki/Malbolge
[+] [-] pronoiac|7 years ago|reply
[+] [-] wodenokoto|7 years ago|reply
https://youtu.be/VIVIegSt81k
[+] [-] ygra|7 years ago|reply
[+] [-] emmelaich|7 years ago|reply
That explains a LOT. As in most descriptions of it are annoyingly ambiguous.
Whereas if you knew the game, you know it already.
[+] [-] thrmsforbfast|7 years ago|reply
My very first interviewer (intentionally) didn't spec fizzbuzz correctly. The real test was whether the candidate listened to the customer's/lead engineer's spec instead of jumping to conclusions.
Fortunately, I was just entering college and hadn't heard of fizzbuzz before. I passed the "test" but for the wrong reason.
[+] [-] tracker1|7 years ago|reply
[+] [-] stevekemp|7 years ago|reply
https://github.com/skx/gobasic/blob/master/examples/15-fizz-...
Perhaps not the cleanest, since I support neither `CASE` nor `ELSE IF`. But it seems to be correct.
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] grahamotte|7 years ago|reply
[+] [-] Retr0spectrum|7 years ago|reply
[+] [-] geraldbauer|7 years ago|reply
[+] [-] ErikAugust|7 years ago|reply
[+] [-] daphneokeefe|7 years ago|reply
[+] [-] equalunique|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] tne|7 years ago|reply
[+] [-] 333c|7 years ago|reply