The other day I asked for an analysis or at least an UML diagram since we are having quite some troubles and my boss looked disgusted at me for asking such a question. I’m not a professional backend developer, so I don’t know how it works professionally
I understand the predicament you are in, but I don’t know that you’ll get very far with your current approach.
The actual artifact you need from your collaboration is the list of API endpoints and the structure of what the request and response payload will look like for each one. This doesn’t need to be UML, it can literally be a text doc.
By asking for something highly structured that the other people may not know how to make, or do not have the tools to make, you’re putting them in a position where they have to acknowledge that they don’t know how to do something, or causing them to do work that they don’t value. Once you’ve had success on a team and developed trust/respect, you can push for adding process/tooling, but if you’re new to a team, you really have to work with what you’ve got.
Either of you could write a simple doc outlining the API and then collaborate on that (it’s also much easier to actually comment/collaborate on than a diagram, anyway).
I think you misunderstood, I’m the one implementing the API and writing the queries - alongside a coworker that doesn’t have BE experience. I’m not the one who made the DB though, neither is he, and the design is not very reliable