The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
FizzBuzzEnterpris Alternatives
Similar projects and alternatives to FizzBuzzEnterpris
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
FizzBuzz Enterprise Edition
FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
-
intellij-plugins
Open-source plugins included in the distribution of IntelliJ IDEA Ultimate and other IDEs based on the IntelliJ Platform
-
Graal
GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
ponyc
Pony is an open-source, actor-model, capabilities-secure, high performance programming language
-
tinygrad
Discontinued You like pytorch? You like micrograd? You love tinygrad! ❤️ [Moved to: https://github.com/tinygrad/tinygrad] (by geohot)
-
runtimelab
This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.
-
AspNetCoreDiagnosticScenarios
This repository has examples of broken patterns in ASP.NET Core applications
-
Scrawl-canvas
Responsive, interactive and more accessible HTML5 canvas elements. Scrawl-canvas is a JavaScript library designed to make using the HTML5 canvas element easier, and more fun
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
FizzBuzzEnterpris reviews and mentions
-
Java 21 makes me like Java again
> I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)
You can write that kind of crap in any language, including C++.
-
No One Wants Simplicity
There’s a difference between complexity that’s inherent to the problem, and complexity that’s added by developers who have drunk architectural cool aid.
This is an example where all of the complexity is caused by rigid adherence to the most popular architectural patterns of about 10 years ago.
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
It looks completely ridiculous to modern eyes, but during peak OOP it was just how you should do it.
If you like simplicity then your fizz buzz implementation would be a few lines.
-
Virtual Threads Arrive in JDK 21, Ushering a New Era of Concurrency
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... isn't too far removed from some of what I've seen in big tech, especially architecture-wise. Certainly less costly absurdity.
-
Subverting the Software Interview
What you need is Fizzbuzz, Enterprise Edition
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
- Every day, I commit a new and more complicated version of some simple code
-
Ask HN: Why do you make class members private?
It's been a decade since I used C# but the corporate design pattern culture of that language back then turned me off of it forever.
Everything looked like this: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
Maybe it's better now but the Java/C# practice of shoveling largely empty classes around with an IDE isn't something I'd point to as a good example.
-
Why DRY is the most over-rated programming principle
```
With your example I had to think for about 1-2 min before it made sense. If the codebase is full of clever stuff then I have to spend hours understanding all of the clever things before I can make changes. If everything is simple then it's easy to change.
If you want to see where overengineering leads you then take a look at this project. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
It is satire but I have absolutely worked in places that write code like that.
Good programmers know that it's 10x times harder to read code than write it, so they deliberately keep it simple so that they can read it later.
-
Why programmers are not paid in proportion to their productivity
I did something similar a 4 or so years back. I wrote something in a month (+ a couple of working with stakeholders to make sure it did what it should). I did it in a legacy tech stack that the architects didn't like, on the side of the main activity, as the deadline was coming close and some hireing processes were slow.
A team of around devs 5 (some coming and going) having been trying to solve the same problem since, but they're still not being close to finished.
In other words, the productivity is in the order 50x to 100x slower than when I did it. Rather, the main reason was that I knew how to write code like that, while they were set up to fail.
Basically, some architect was making all sorts of unnecessary demands for how to wite the code, and the programers were not familiar with much of the tech stack that was introduced.
Also, coding standards were really verbose, easily 10x-30x what I wrote, in lines of code. The current state of what they have look suspiciously like FizzBuzzEnterpriseEdition:
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
TLDR; Incompetent tech leadership prone to cargo-culting, can slow down productivity to virtually zero. In some cases, productivity can go up by ~100x if ignoring their demands.
-
The use of `class` for things that should be simple free functions (2020)
I swear I've worked with people who if they were shown FizzBuzzEnterpriseEdition wouldn't be able to see the joke as that's how they naturally write all code.
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
-
The mindless tyranny of “what if it changes?” as a software design principle
Reminds me of FizzBuzzEnterpriseEdition . https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
You never know when you might need to change the implementation of how the "Fuzz" string is returned, so you need a FuzzStringReturner.
And you never know when you might need multiple different ways of returning "Fuzz", so you need a FuzzStringReturnerFactory.
And that barely scratches the surface of what you need.
-
A note from our sponsor - WorkOS
workos.com | 24 Apr 2024
Stats
Popular Comparisons
- FizzBuzzEnterpris VS FizzBuzz Enterprise Edition
- FizzBuzzEnterpris VS holochain
- FizzBuzzEnterpris VS lwjgl3ify
- FizzBuzzEnterpris VS proposals
- FizzBuzzEnterpris VS fibers
- FizzBuzzEnterpris VS music-explorer
- FizzBuzzEnterpris VS manifold
- FizzBuzzEnterpris VS latte
- FizzBuzzEnterpris VS tinygrad
- FizzBuzzEnterpris VS AspNetCoreDiagnosticScenarios
Sponsored