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.

Explore on GitHubRead Hacker News discussions
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, 6:01:08 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

15 sources
Sohcahtoa82·Jun 19, 2017
I kinda wish the code for the Clojure and Java implementations were posted. In my limited Java experience, I've found that Java itself is fine, but for some reason, professional Java developers stick to these crazy idioms that result in these monstrosities of code. I'm sure we've all heard of FizzBuzz Enterprise Edition[1]. It's satire, sure, but every dollar of satire contains a couple cents of truth. I bet the Java version of that Spark job could have been done in under 100 lines of Java, but it was divided into 7 files totaling over 400 lines of code because there's this feeling that you're "supposed" to write Java like that. EDIT: Back in college, I took a machine learning class and wrote programs that would load training data, use it to classify data, and output results. I did all the tasks in a single .java file. If I were to do
Read the rest
it following Java idioms, I probably would have needed to separate the code that read the training data into a TrainingDataLoader class, the code that classified data into a DataClassifier, and then used a DataPrinter class to output it all, plus a main class to pull it all together. Great, my single file, ~200 LoC project is now 4 files and gained dozens more lines of boiler plate to pull it together. Stop writing stupid Java code and then blaming Java for your code being stupid. [1] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
In Java may be verbose, but who cares?
treehau5·Mar 27, 2017
> While in the JS world, even now that browsers are starting to support ES6, everyone just adds more and more steps to the build process, instead of trying to simplify them. To build on your Java comparison -- this is would be akin to using a new feature that is still in the JSR approval process, and then downloading an edgey JVM platform (maybe OpenJDK nightly, or something like that) and then complaining when your app gets more complicated. The solution to that problem is to stick to the stable syntax until the new becomes fully supported. Admittedly, this is a problem with browsers where instead of 1 environment, there are 8 with some 1 offs, but again, there is IBM JDK, OpenJDK, Oracle JDK, Android Java (whatever that's called, Dalvik or something?) > The problem is that the JS world is simply more complex than the Java world. I stro
Read the rest
ngly disagree. Have you seen "enterprise fizzbuzz"?* I don't mean disrespect but you are kidding yourself if you think Java isn't as complex (if not more) than the current JavaScript ecosystem. I spent 6 years programming in Java and never felt I scratched 10% of the surface. * https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
In Next.js 2.0

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.