The EVILEST code to ever exist 💀💻 #programming #technology #code #software #tech #programming

[LCTesla]

Solid principles: single responsibility
Programmer: the responsibility of this class is to do everything, thats one thing right

[soppuistoppu]

I once wrote in my friend's code "#define true false". Now I have no friends

[nnavu]

if (isFirstLoginAttempt) return "Wrong pasword"
The most "evil genius" code in my opinion :)

[CommentGuard]

I wrote a single file that was 20k lines that had everything.

I got a bug report saying "I don't want to read it"

[FZs]

That "error handling" is actually pretty common in embedded, where there's no OS to abort the program on critical failure, so busy looping is a way to stop the processor from doing something harmful (e.g. corrupting stored data) by continuing in an invalid state.

[term]

Someone doesn't know the difference between encryption and encoding 😅

[JC-shim]

Base64 thing is real.. I've seen a guy post his real password in public documentation, "encrypted" like this. If it looks cryptic, it is encrypted !

[dev-rwoj]

Fun fact: such infinite loop usually used at embedded software(like STM FW etc.) to handle hardware initialization errors.

[wheresecretslie]

one function that does “all” is that even possible 😂

[shidhartharoy]

One function is just evil.


This comment has more likes than Lewis😂.How??

[patrickshepherd]

Lol! That infinite loop looks like it was written by a programmer who felt they weren't being listened to and wanted to test whether that was true or not.

[alt]

The most evil cod is what crowdstrike pushed not so long ago

[saumytiwari]

I laughed so hard after listening that the guy is returning base64 encode and thinking he is now secured
😂
It is like,
You are hiding your house key beneath the doormat

[ShorlanTanzo]

A dumb programmer: Makes mistakes that they have to fix later.
A smart programmer: Makes "mistakes" that they have to "fix" later.

[jimsackmanbusinesscoaching]

Most evil code I ran into. Hired as a contractor to fix code that the client had gotten for free from a vendor. It contained a single comment: "If you can figure this out, you are a better man than I." Which given that this was a pointer to function call based on a set of tables that were calculated at the time of program start took me a couple of weeks.

[declanmoore]

I'm guessing the infinite loop case was probably to make it super obvious that an exceptional case has occurred? At least if you have debug symbols enabled, it should be readily apparent where the code is stalling and know that you need to fix something. Debug log or breakpoint would have helped though.

[kejax]

I love that we're all using the same site for base64 de- and encoding
<3

[Zeero]

Programmers with experience being an administrator knows that you can always store shared passwords on the server in clear text so long as the server itself has controlled access. However, if security is poking around, base 64 helps avoid a hit, because they rather see that than nothing. Of course, these days we're heavily dependent on 3rd party tools that require plain text passwords on servers to access a database, keystore, or backend service, so now security doesn't do that kind of scan anymore. They just want to make sure that server access and file permissions are locked down.

[biscuitstix_]

that password “encryption” is just VILE

[anonymous]

You had me a 'encrypt password' - encrypting passwords at all is incorrect; encryption is two way, you need a one way hash, so you never know what the password actually is either.
So even if you ACTUALLY encrypted it (AES, chacha, et al) - instead of base64ing it, then you're still doing it wrong...