I have this: https://github.com/LanceH/fizzbuzz in my back pocket just in case it is asked in an interview. I have the seed memorized to put in last while they're wondering what in hell I'm doing.

If the interviewer can't handle my sense of humor, then I'm not working there.

This is awesome!

Cutesy reminder that regular fizzbuzz still filters out almost half of the candidates I receive for junior dev positions.

Some because they don't understand the requirements, some because they don't know how to use loops, some people they don't know how to use conditions, and yes some because they make overly complicated mess for no reason, or to try to be "super smart".

>because they make overly complicated mess

https://thedailywtf.com/articles/The-Fizz-Buzz-from-Outer-Sp...

Hah, I remember having no clue what was going on the first time I read that, but it clicked just now. The fizzbuzz problem as described in that paragraph could almost be interpreted as 3 equations. The math was for something along the lines of this problem:

  x = fizz / 3
  x = buzz / 5
  x = (fizz * buzz) / 15

In this system of 3 equations, what is "x"?

Not sure what's going on with the 1-100 though.

Enterprize FizzBuzz has been one of my favourite things for a while. It perfectly captures the attitude where I used to work, where people felt that by adding later upon layer of obfuscation they were doing engineering.

This was a lot more fun before Github started collapsing directories of one item!

That makes it more fun because you never know when the rabbit hole will end.

This is hilarious and eerily real world like.

Be sure to check out the issues, too :)