Neat text. I'd be really impressed if I were to interview him, but then again: I'd never ask someone to write a fizzbuzz... hmmm...
Edit: I actually tried a FizzBuzz myself and I actually like it. I get why people were to ask it at interviews since it does require you to think for a second (if you haven't done it before) so you can easily filter out people who can't think
Highest professional enterprise standards my arse. Where's the message queues? Why isn't there a Fizz microservice and a Buzz microservice that live behind an API Gateway and receive messages from an event driven architecture?
I'm gonna need a write up. I've been looking at the code for 10 or 15 minutes and I still haven't found "fizz", "buzz", or the number 100 anywhere in the code. It's amazing.
I think it’s really shortsighted to hardcode them statically into constants. You’d have to build a completely new binary should the requirements someday change! Obviously they belong behind a configuration interface, an instance of which can then be dependency injected to places that need them. In this way you can easily supply them from whatever source you like, such as a properties file, XML document, a database or even a web service.
Many many years ago I did a project building a functional programming language that macro expanded into lambda calculus that was then compiled down to SK combinators for evaluation. This was entertainingly inefficient.
I'm tempted to resurrect the code (I still have a printout) and use it to implement Fizz Buzz....
Edit: I actually tried a FizzBuzz myself and I actually like it. I get why people were to ask it at interviews since it does require you to think for a second (if you haven't done it before) so you can easily filter out people who can't think