Scrum is a scam to create more jobs for business majors.

I have a disagreement with my product owner (PO). Our team develops APIs in Mulesoft. We've got a release coming up and PO wants to release one of the APIs that has *some* working endpoints, but other endpoints in that same API have some open bugs.

Given that it's *unlikely* that those broken endpoints will be used, does it seem like good practice to release the API with known bugs in it to hit the deadline?

Understand that we're not just releasing the working endpoints. We're releasing all of it, bugs and all. PO's logic is that those broken endpoints won't be used therefore it's fine to send known bugs into production.

I just need some advice in dealing with this

I could use a few more non-technical people telling me how I can do my job better.

Dataweave is a programming language like pornstars are actors. They are _technically_ acting but there’s a difference…

Edit: though I would never talk shit about pornstars like I do dataweave

Say your boss keeps going out of his way to create new positions, and giving them to people without interviewing anyone. Am I wrong for being upset/annoyed by this? They aren’t even positions I wanted. Idk why it bugs me so much…

I linked the wrong week for my no. 1 answer so for this one I’m gonna go with: somehow swing a law-enforcement-adjacent job despite my copious cannabis consumption.

To make a semi-meaningful (or really any kind of) contribution to the Linux kernel. Like just to leave something useful behind in general.