I just fucking despise working on someone else's code and it's filled with errors like "reciever" instead of "receiver" or "mesasge" instead of "message"...

it fucking leads to an astonishing amount of fucking errors just because I know how to write english words AND I'M ITALIAN WTF

That must make for a lot of spaghetti code

Sorry

@alexbrooklyn don't worry! I enjoy pasta like I enjoy my code: short

I don't mind.

Usually I don't even read names of variables. Auto complete is there for that

It's like they weren't paid exclusively to write that shit.

Files under: copy pasta mistakes

Haha well, imagine a 1000+ warnings on the use of == instead of === and != instead of !==. Now add in those spelling mistakes and put them in a react component that's 3000+ lines because SOME JACKASS REFUSED TO LEARN HOW TO USE REACT PROPERLY AND TURNED INTO A GODDAMN TEAM LEAD.

I know you're out there, I know you're watching. I have my eyes on you, you lousy '==' bastard.

I have had a dyslexic dev coworker naming stuff like amount (money): cash.. but then with his dyslexia on top it becomes cache. Imagen db columns named cache_amount... He's a nice guy and all but stuff like that can be really confusing at times.

@ImNotAlfred is there not a code review step that prevents that code from getting in?

@alexbrooklyn Guess.

@alexbrooklyn you would think so. This all happened before I started working there, but even now the lead of that project in question thinks code reviews are a waste of time. For that reason alone (there are hundreds more) he shouldn't be lead. But he is with the company the longest and knows the most about that codebase because he wrote alot of it himself. Management thinks a dev who knows the codebase best, makes the best project lead, which is wrong. But I didn't want to work with him anymore because of the endless discussions about code quality vs ticket quantity and they approved my demand.

There where alot of discussions that went like this:
Him: I want you to use option A

Me: why, I think option B is more readable.

Him: Option A it alot faster and everyone uses option A

*Me looking up what community has to say about A vs B.*

Me: hmm could you link me that article where you found that information because on forumX and forumY the majority appears to pick B over A.

Him: Doesn't matter, A is still faster.

Me: to settle that point we could whip up a script that iterates both 10.000times and return the time difference.

Him: that's a good idea, then you'll see.

*He writing the script to make sure I don't cheat somehow*

Result : B is 33% faster on average
(He ran it multiple times to make sure)

Him: we are talking about milliseconds here, thats neglectable..

Me: true but then it comes down to semantics and then it really doesn't matter.

Him: you have to use A tho.

Me: why is that ?

Him: cuz I said so, and I'm lead. When you are lead you can make those directions.

Yes, fucking hate that, i have a spellchecker plugin in VS code, and it has helped me fix grammatical errors instantly.

@ImNotAlfred you should post that as a rant haha

Sometimes its massage.

@manjrekarom I'd like to have one when I see this kind of stuff haha

My favorite is when those errors are ignored by the other devs too, and then it gets baked into the code so deep you can't even refactor it and everyone tells you "yeah, we need to keep that typo in, cause It's already referenced through 20 services and fixing it would break everything"

Oh I hate that so much! I have spellcheckers, why can't they use that?! Sometimes I couldn't find the variable cuz it was so fucked up. And when you're done refactoring, you think, another one pops up!

@ZioCain haha yeah