"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.

when you're copying code from stack overflow and you have to change the class names

Just needing to vent a bit...

We start off with classic asp.net & Xamarin. K.

Then we run into the shitshow that's lackluster documentation and heavy push for asp.net core.
Whatever, will just handroll things.

K. Azure is quickly turning expensive..
Well let's find alternatives.

Yeah, no Linux ain't gonna work.
Wanna shell out for a windows server? Nah.
K. Well, let's rewrite in asp.net core then.
Nginx proxy passthrough to kestrel. Ez.

Now.. wtf is the deal with mssql behaving like a turd on Linux?
Oh now some security jibber about telemetry and adding Microsoft keys to root.

Whatever. I can do PHP & MariaDB then.

1001 things wrong about Xamarin now.
Mostly performance related.
Especially cuz custom renderers for everything.
& Abused onPropertyChanged.

Uh la la, look at that sexy thing called react native.
Hippytyhop new tool for the job.

Ugh wee, what's this ? Customer impatient & deadline for months worth in Xamarin => 1 week.

Whelp I be fudge..

Trying to build a ros workspace inside VMware...
Called up the teammate who put it together:

Me: hey the workspace isn't building for me, do I need to setup anything before I type "make"?

Him: nah dude just type make and ur good, why what error are you getting?

Me: *describes error*

Him: oh lol I never got that error before, idk maybe your machine is just dumb

Me: *uh ok sure dude* let me try some other stuff
*Boots to native install of Ubuntu*
*Build successful*

Me: oh huh that's weird it built on my native installation but not on the VM

Him: oh lol that's not my problem

Seriously dude? First off, screw you Ros for not being able to build in a VM. Secondly, it's entirely your problem! Linux is nice to use, sure, but it's a bit of a problem when the entire team runs off Mac!

😲😲😲😣😥😫😓