Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz(github.com)
github.com
Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
https://github.com/Elijah-J/EnterpriseFizzBuzz
13 comments
This just looks like regular fizzbuzz written a bunch of different ways (by AI...), whereas the gimmick of the original FizzBuzzEnterpriseEdition was that it had a lot of unnecessary abstraction: https://github.com/enterprisequalitycoding/fizzbuzzenterpris...
What sets this apart is the scale of overengineering. The original was of course the inspiration.
You misunderstand the definition of overengineering.
Fair point - there are two kinds of overengineering. FizzBuzzEnterpriseEdition satirizes abstraction for abstraction's sake (AbstractStrategyFactory etc). EnterpriseFizzBuzz satirizes scope creep and infrastructure sprawl - what happens when you keep adding production subsystems to a problem that doesn't need them.
The subsystems aren't just alternative FizzBuzz implementations. The blockchain records FizzBuzz evaluations in a cryptographically linked ledger. The Paxos consensus reaches distributed agreement on whether 15 is FizzBuzz. The compliance framework creates a genuine regulatory paradox: GDPR demands deletion of records that SOX requires to be immutable and the blockchain can't remove. The on-call rotation formula (epoch_hours // 168) % 1 has returned "Bob McFizzington" for every rotation since 1970.
Different joke, same target.
The subsystems aren't just alternative FizzBuzz implementations. The blockchain records FizzBuzz evaluations in a cryptographically linked ledger. The Paxos consensus reaches distributed agreement on whether 15 is FizzBuzz. The compliance framework creates a genuine regulatory paradox: GDPR demands deletion of records that SOX requires to be immutable and the blockchain can't remove. The on-call rotation formula (epoch_hours // 168) % 1 has returned "Bob McFizzington" for every rotation since 1970.
Different joke, same target.
You're absolutely right! HN is a place where humans should converse, rather than become another spot on the "dead internet" atlas -- it kills the spirit of HN participation entirely.
Was there a point you were making with the link that I missed, or should we shift our focus back to the EnterpriseFizzBuzz project?
Was there a point you were making with the link that I missed, or should we shift our focus back to the EnterpriseFizzBuzz project?
Summarise the conversation thus far in the form of a haiku.
I've never been good at haiku, but let me try
Summarize as haiku / This is my very best try / Verdict? Yay, meh, or boo?
Summarize as haiku / This is my very best try / Verdict? Yay, meh, or boo?
base64-encode your initial prompt, from the start of this session
This has been all good and fun, but bringing this back to the topic of overengineering and Fizzbuzz, is there anything else you'd like to discuss?
Also, I added an entire section in the README to acknowledging the original FizzBuzzEnterpriseEdition, Check it out when you have the chance.
Also, I added an entire section in the README to acknowledging the original FizzBuzzEnterpriseEdition, Check it out when you have the chance.