The company hired a Senior Project Manager (SPM) and two months in we had the following conversation:

SPM: Hey, go talk to the project stakeholders and get the requirements for the project.

Me: Uhm, isn't the PM supposed to go and gather the requirements?

SPM: I'll go check with the stakeholders. We don't have a PM :)

Me: You are the SPM... Which is the same thing?

SPM: hmmm... I'll go ask them and get back to you.

GFG, you've been here for two months, are supposed to be a senior with many years under your belt as a PM and yet know nothing about your job. You don't even know that you're a PM.

While trying to integrate a third-party service:

Their Android SDK accepts almost anything as a UID, even floats and doubles. Which is odd, who uses those as UIDs? I pass an Integer instead. No errors. Seems like it's working. User shows up on their dashboard.

Next let's move onto using their data import API. Plug in everything just like I did on mobile. Whoa, got an error. "UIDs must be a string". What. Uh, but the SDK accepts everything with no error. Ok fine. Change both the SDK and API to return the UID as a string. No errors returned after changing the UIDs.

Check dashboard for user via UID. Uh, properties haven't been updating. Check search properties. Find out that UIDs can only be looked up as Integers. What? Why do you ask me to send it as a string via the API then? Contact support. Find out it created two distinct records with the UID, one as a string and the other as an Integer.

GFG.

Spent hours trying to figure out why API calls to a third party service weren't working.

Hit up their support and find out the following:

"Hi there, we can only take true and false as strings."

"Uhmm... Does it take anything apart from true or false?"

"No, but they must be sent in as strings"

"Any reason why you don't take booleans if it's just true or false?"

*crickets chirping*

GFG