Our issue is that we hired an intern to code FizzBuzz, and he mistakenly coded it as divisible by 3 for Fizz, divisible by 4 for Buzz, and divisible by 13 for FizzBuzz. Now, our sales force runs on this modified FizzBuzz. We cannot simply accept an additional unvetted FizzBuzz, even if it strictly adheres to the standard.

This version on GitHub looks solid, but it needs an Enterprise Compatibility Mode that loads an external emulation mode for modified Fizz, Buzz, and FizzBuzz values in order for adoption to take place.

You can buy that as an add-on, a consultant will install that within only a few months.

When you do add Excel functionality, please ensure that it supports Excel 95 fully, as we need it to be compliant with our bidding solutions for government contracts.

We have a proprietary method for up-converting it before bidding on military contracts.

And LDAP authentication.

If I didn’t have twelve other things going on right now, I would totally file a PR for that.

But there are so many flavors of CSV file to choose from. So I’d have to make that pluggable too.