A while back, I ranted about emojis in code.

My nightmares are becoming reality.

Behold, production code:

When writing a JavaScript guide, please don't use emojis as keys in objects. Or anywhere else in code. Zoomers will think it's common practice.

Just because you can, doesn't mean you should.

Sincerely,
everyone

Naruto-run to get coffee while project compiles

Wtf is up with all the advertising posts nowadays? I see atleast two every day

"We use top of the art, endgame, final boss, super technology"

What they actually use: Java 1.8, jQuery, JSP and an old version of bootstrap

Why is this still a thing?

Is the search functionality broken?

me and my co-workers: "lmao lets see if this github copilot is so great as they claim"

copilot: *solves issue we've been working on for 8 hours, in 10 seconds*

me and my co-workers:
(┛ಠ_ಠ)┛彡┻━┻

Client: "When will feature X be ready? How much time to you need?"

Me: "Well, considering the size of the feature it will probable ta..."

Client: "You have exactly 8 minutes to finish or I'll throw a tantrum."

A bit exaggerated, but it pretty much sums up my job.

"It works on our end", the sentence that made me lose my shit.

I've been working on a project were we're supposed to integrate an API into our system.

When trying to get some user id's (UUID) from said API, we got a type-error in the response (???), so I called their integration support and asked what the fuck they were doing (not really, i was kinda calm at this point).

The answer I got was following:

Integration guy: "Uh, bro, like, I don't even know, it's probably on your end"

Me: "We literally used this endpoint with the same parameters yesterday, and got a result we expected. I noticed you updated your API this morning, did you make any major changes?"

Integration guy: "Yeah we changed the type of user id from string to number"

Me: "So, you changed the type of a UUID (uuid4) from string to number? How did you not think that would be an issue? I can see in your forums that everyone else is having the same issue."

Integration guy: "Nah, it's probably a bug in your code, it works on our end"

Me in my mind: *IT WORKS ON YOUR END?!? IT DOESN'T FUCKING MATTER IF IT WORKS ON YOUR END, FUCKTARD.*

What I actually said: "Uhm, I'm not sure if works on your end either, I'm not even sure how this change made it to production. But hey, thanks I guess, bye."

WHY AM I NOT ABLE TO YELL AT PEOPLE WHEN THEY ARE BEING RETARDED???

But really though, when you're maintaining an API, you shouldn't fucking care if things work on your end in your dev environment. What matters is how it works in production, for the end user/users.

And I know that 99% of cases it's the users fault by entering the wrong parameters or trying to request with wrongly setup auth and what not, but still.

Don't ASSUME nothing's wrong on your end. It's your fucking job to fix the issues.

And guess what? The problem was on their side.
I'm going fucking bald.