Ok, so our team is responsible for writing an app that consumes an API written by the client's team (I refuse to call it a "REST" API, despite their claims). On one of the clarification meetings we are discussing an endpoint that accepts a (logically) unique field multiple times, even though an entity is already registered in the system with that unique identifier. Our proposal would be that this API of theirs should not happily accept duplicates as many times as there are bits on a 4TB hard drive, rather it should signal an error.

The response we got is this: Due to the Separation of Concerns principle they thought that it should be our app's responsibility to not send a request if an entity with said field is already in the system. Thus there's no need for the backend to validate this.

I didn't hear the next part, because I had to collect my headphones from the other side of the room where they were flung in rage.

I just hate it when Windows dies in obscure ways just when you need it.

This is why I use Linux most of the time, but hey, I thought it would be nice to finally play a game now that I've got a couple of days off. So because the big titles still don't want to support Linux, Windows was the only choice. Second day in, it won't log in to the system, rebooting to recovery mode is either excruciatingly slow or not working and I bet a virtual racoon died inside the Windows installation just for the hell of it.