It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

Dells XPS are made of magic. [long story, major fuckup, 10k+ damages]

It all started in December. One morning I was late to work, drove there as fast as possible. (I live like 3 minutes away so me being late really meant *late*) Parked my car in a secluded car park, grabbed my backpack and ran to work. The car park is like 100 meters away from work so I took my feet into my hands and ran. Next thing I know my heels loose all grip while I go down a small slope and I drop on my back full force. On a sharp edged stone. With only my 1700$ XPS in it. Fuck.

I paniced, but got up and ran to work. I checked on the notebook, praying it would boot. It booted! Holy shit. I flipped the notebook and saw two small dents in the aluminum shell. I was thorougly impressed. I later discovered that it left a small shadow on the display, but given what a hit that was (I am not exactly a lightweight), impressive would be a massive understatement.

Fast forward to February, I am weighing my options to get the screen replaced maybe, as damage on my hardware (even if neglectable) triggers some sort of OCD and makes me feel bad 24/7. Also my laptop tends to shut off from time to time, looked into the Event Viewer and saw kernel panic. I figured that the battery probably still took a hit and that it drops voltage from time to time and the kernel assumes a critical situation, thus shutting off.

It stayed quite snowy in Austria up until March, so occasional snowing wasn't rare. Got out of work one day, saw it snowed a bit. Whatever. I had my moms car at the time, so I tried if it would slide a bit if I donut on the now (5pm) empty parking space. Nothing. Drove done a small hill, ABS triangle lit up red (board computer can't outbalance the snow). I drove out to the main street where everything was salted and drove along towards my house. Took a turn into my street, accelerated for a bit and then went off the gas so the car would smoothly drive along with the speed slowly degrading. So I went off the gas and noticed I was a bit to the right, no wonder, centrifugal forces.

*steers left*
"Huh seems like I need a bit more"
*car still doesnt move much*
"What the- go to the left!"
*steers left hard*
"Fuck that wall is coming closer"
*Breaks*
*car doesnt break*
"FUCK FUCK FUCK FUCK!!!"

Everything got quiet in seconds, me waking up to an open airbag, ripped pants, a hurting wrist, the radio somewhere on the ground and fumes that smellt like burning wires. I grabbed my backpack that was now somewhere on the floor instead of on the seat and ran outside, tears in my eyes and the phone on my ear calling my mom. I walked inside as she walked outside, hearing a weeping scream that I haven't heard from her since I am alive. While walking inside I noticed my backpack was wet on the bottom, my 2 litre water jug shattered when my backpack hit the dashboard. I tried to stay calm and act rational, knowing that every second counts when It comes to water damage. I hastely searched for some rice and a bag to put my laptop into, stuffed the bag with both and went outside. The car was totaled, my mom pissed and crying. And I was in shock, sad, angry and hurting.

I kept the laptop on my heater for a few days, bagged in rice. I dared to try a boot after a while and you wont believe me, it fucking booted. Even the keyboard backlight worked, just the screen was obviously broken in the back (no color distortion or bad pixel rows though!!) and the aluminum shell had a dent on the front. I talked with Dell Support a few days later, asking if it would be ok to open the XPS up so I could drain all of the water. She said yes thats fine, as long as I dont touch anything or screw around with it.

She said I can send it in and get it checked, but the pickup and analysis will cost 150$ and I can go from there.

I sent it in and estimated that, because battery, screen and other things probably needed changing, it will be around 900$.

Got a call a few weeks later:

"Hello beggarboy, the repair team reported back to us and said that they will have to replace everything, which will be 1700$."

"Fuck... Buying a new one is cheaper.."

"Yeah I know I am sorry about that, I can offer you a voucher so you can buy a new one for 250$ off if you would prefer that"

"Sorry but I will need some time to consider"

"I understand."

The agent clearly noticed I was bummed about it.

After going back and forth what to do I got another call a few days later.

"Hello beggarboy, we talked a few days ago. I have good news"

"Hello, yes, speak up?"

"I was able to get a special offer for you after putting in a few words..."

The next thing she said seemed unreal to me.

She was able to cut 600$ (!!!), making the new offer 1100$, instead of 1700$ or a new one for 1500$. I figured the reason she probably did that was because I am always very polite with support members. Always.

My XPS is back and healty again.
Thank you for taking the time to read this.
Dells XPS are made of magic.