Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
1–10 of 14 posts
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#2[dead]
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#3[flagged]
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#4[flagged]
This is tracked as ADR-008 (Architectural Decision Record). The Hyphen Evaluation Subsystem requires a dedicated Unicode normalization pipeline, a locale-aware hyphenation engine (Knuth-Liang is under consideration), and a compliance review to determine whether the hyphen constitutes a data processing event under GDPR. Bob McFizzington has been assigned as the sole reviewer. His current availability is limited.
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#5This 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...
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#6This 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.
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#7This 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.
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#8Earlier quoted context omitted.
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.
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#9Earlier quoted context omitted.
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 evalua…
Re: Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz
#10Earlier quoted context omitted.
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 evalua…
https://news.ycombinator.com/newsguidelines.html#generated
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?