search

EnterpriseQualityCoding / FizzBuzzEnterpriseEdition

FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
21.55k stars 761 forks source link

Our code is both unsecure and unsafe. #563

Open croissant676 opened 2 years ago

croissant676 commented 2 years ago

I have come to realize that our supposedly 'enterprise grade' fizz-buzz program isn't even ready for deployment at all. There are several problems that I have identified. Firstly, our code is readily available on https://github.com, which means that anyone can run our application. To prevent others from maliciously running our code, I propose that we make our unrunnable.

Another problem that I identified was that our code is still a monolith. As a 'enterprise grade' program, our code should've been split into microservices a long time ago. This should be a top priority for our backend development team.

Finally, corporate that an immediate transition to a REST API would maybe improve our profits. On a side note, there are certain aspects of our current implementation that I believe can improved. For instance, instead of storing all our data in memory, which is high inefficient and unsecure, we should instead store our data in our new FizzBuzzSQL database. If the development team finds using such a product to be too unreliable, corporate has allowed them the freedom to store data in plain text.

Tylersuard commented 2 years ago

A question: how can we tell if someone is running our code maliciously, as opposed to benevolently?

croissant676 commented 2 years ago

One way to tell whether they are running it maliciously is by seeing if they run it on a computer or not. Those who run it benevolently are sure to run it on the newest Brick server. However, computers contain scary things like the JVM, which can run illegally modified instances of our code.

croissant676 commented 2 years ago

After a week of deliberation, Mark agreed that instead of attempting to make this unrunnable (which would require deleting all the files), we could instead make our code malicious. This way, when the malicious people attempt to run our malicious code, malicious software will be injected into their malicious computer, maliciously reducing the amount of malicious harm they can maliciously cause to others.

ghost commented 2 years ago

No it isn't. Stop making these things up or else you're fired.

Sincerely, Son of Former CEO, CEO of EnterpriseQualityCoding.