HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
EnterpriseQualityCoding
FizzBuzzEnterpriseEdition
Java2013–2026
EnterpriseQualityCoding / FizzBuzzEnterpriseEdition

FizzBuzzEnterpriseEdition

FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.

216Distinct people
237Mentions
3Explicit recommenders
23.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Issue #393 - "My printer isn't working" is a highly recommended read in this repository. Every time I thought it couldn't get any worse, someone posts another atrocity. It's a…

ahofmann used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year237 dated mentions

Observed mentions: 2013-03-18 16:29:35 UTC to 2026-10-31 00:51:11 UTC.

01020302013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 14 mentions; 6 submissions, 8 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 19 mentions; 4 submissions, 15 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 15 mentions; 2 submissions, 13 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 19 mentions; 0 submissions, 19 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 16 mentions; 2 submissions, 14 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 23 mentions; 1 submissions, 22 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 28 mentions; 3 submissions, 25 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 19 mentions; 0 submissions, 19 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 19 mentions; 1 submissions, 18 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC1468
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC15312
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC11011
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC19415
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC15213
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC19019
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC16214
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC11011
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC23122
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC28325
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC19019
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC15411
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC19118
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC13013

What Hacker News says

237 sources
I've never heard of Ponytail before, I've read the entire README and glanced through this repo and I'm left so confused. From what I can gather this project is essentially a single markdown file with a prompt that verbosely says "write the simplest code". Yet the repo itself looks so bloated and complex and has so much activity. This feels like satire similar to fizzbuzz enterprise edition[1] but apparently this is the actual state of our industry? [1] https://github.com/enterprisequalitycoding/fizzbuzzenterpris...
In Cisco gives engineer unlimited AI tokens to rewrite legacy code
Yes, well, so can humans given the "right" circumstances, e.g. "enterprise" software: https://github.com/enterprisequalitycoding/fizzbuzzenterpris... Assuming the code is produced to serve human needs there will be humans in the loop somewhere. Not nearly as many as before and not in the same roles but they will be there The advent of the Spinning Jenny, water frame and power loom (etc.) changed textile manufacturing for good and made the end result so cheap that it is now seen as disposable. There are still some people in the loop controlling the machines but not nearly as many as before and also not really the same people since it takes a different skill set to keep a textile production line running than it takes to spin and weave. The same is true for the advent of the phototypesetting machine (Linotype etc.) and the offset press which
Read the rest
irreversibly changed print production. There are still people in the loop but not nearly as many and with a different skill set. Now what about the "Coding Johnny"? Generative models are now doing the same to coders, irreversibly changing the software production process. There will be far fewer people involved and those people will have a different skill set. Software will become disposable, more like RNA then DNA, if the specifications change the Coding Johnny will churn out a new version.
In How to keep enjoying programming in a world of LLMs
^^^^^^^^^^^^^^^^^^^ I recently wrote a very esoteric Python script. 100 lines of code. No classes, no functions, but yes argparse. I've tried out the latest open source models on the task. They go bananas. It's like Enterprise fizzbuzz (https://github.com/enterprisequalitycoding/fizzbuzzenterpris...). They love classes and imports and reinventing the wheel. A great way for me to tell trash AI slop code is it'll define a useful constant then 15 lines later do it again with a different name. They love making code that looks impressive. "Wow look at all the classes and functions. It's so scalable. It's so dynamic. It validates every minutae against multiple schema and solves a problem I never thought about." But it was trash code. One really was 400 lines and it didn't even look like it would work. Can't even imagine what it means for 4.5M m
Read the rest
oderately good human lines to become what? 27M fluffy filler repeat lines that don't even make sense?
In Formatting a 25M-line codebase overnight
I have seen way too often, advocates of SOLID and patterns to have religious arguments: I don’t like it. That being said, I think there is nothing bad in SOLID, as long as treated as principles and not religious dogmas. About patterns, I cannot really say as much positive. They are not bad per-se. But I’ve seen they have made lots of harm. In the gang of 4 book, in the preface, I think, says something like “this list is neither exhaustive, nor complete, and often inadequate” the problem is every single person I know who was exposed to the book, try to hammer every problem into one pattern (in the sense of [1]). Also insist in using the name everywhere like “facade_blabla” IMHO the pattern may be Façade, but putting that through the names of all classes and methods, is not good design. [1] https://github.com/EnterpriseQualityCoding/FizzBuz
Read the rest
In Laws of Software Engineering
Work may enable altruism outside of your actual job. For example, I got fulfillment from sharing my journey publishing some open source software over the course of a few months. Having savings helped make that possible. SMART criteria[1] can help to get out of a rut. "Making the world a better place" is very difficult to satisfy. How many people? What is better? How much better? I don't advocate for quantising abstract ideas in general but sometimes the thought process of coming up with a number and hitting it helps to get going. My current dayjob involves me wrangling a clunky Java system written like FizzBuzz Enterprise Edition[2]. Keeping this abomination running and getting paid for it feels soulless. Yet I genuinely believe I'm able to stick to my values. For example, there are 3 components tightly coupled to proprietary AWS systems
Read the rest
(AWS Lambda and Simple Queue Service). I feel this has made the world a (very slightly!) worse place; Amazon to me represents the bad side of humanity (greed, scrupulousness). Furthermore, people new to the software dev industry may never know that it's possible to implement these kinds of systems using significantly simpler, portable designs without making a deal with the devil! My goal is to refactor the system to instead use the language's built-in concurrency primitives to perform the same work. The next person who sees the refactored work can more easily take it and run with it without needing to know anything about AWS. That person doesn't need to care either; I can always share this story with others who I don't work with. Maybe AWS does something so egregious that it's distasteful even to company executives; I can confidently say that we're not as tied to AWS as we think. I'm not changing the entire world for all eternity. But in a way I am changing my little tiny insignificant slice of this world today in ways that I hope to inspire even just 1 other person in their own tiny insignificant slice :) [1]: https://en.wikipedia.org/wiki/SMART_criteria [2]: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
In Ask HN: How is your work making the world a better place?
Just as enterprise software is proof positive of no intelligence under the hood. I don't mean the code producers, I mean the enterprise itself is not intelligent yet it (the enterprise) is described as developing the software. And it behaves exactly like this, right down to deeply enjoying inflicting bad development/software metrics (aka BD/SM) on itself, inevitably resulting in: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
In The highest quality codebase

Showing the 15 most recent of 237 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.