You politely break the dumbass’s windows, the mob yanks him out of the car and press his face into the concrete until the police arrive to save him arrest him.
These jackasses think they’re immune to consequences, and that libruls snowflakes are push overs. They’ve been right.
If we don’t defend ourselves, nobody else will. Not the police, not the courts, not the politicians.
But WHY are you trying to make a case for a bad practice? Don’t enable this kind of bullshit, please.
If there’s an error, don’t say it’s 200 OK. Give me something, a 4xx, or at least a 500. Sure, add all you want to the body, but respect the goddamn headers!
This fucks up so many things - starting right with API specs and documentation, s23 (or any other code this crap spits out) are not a part of the pdf file, which is the ONLY available documentation for this 3rd party service. If it serves any internal purpose, I have no clue, but for me it’s useless.
Log analytics is a mess, and you can forget about auto-generating a client, of course…
This is just a huge red flag for me, if their public interfaces look like this, I dont want to know whats under the hood, and I’m actively lobbying for us to change to another provider.
I may have run in your acquaintance work, stuff along the lines of
200 OK
{ error_code: s23, error_msg: "An error was encountered when performing the operation" }
If you happen to run into him, kindly tackle him in the groin for me.
Thanks!
“Can you explain some of the issues with the current administration?”
This guy: Hold my beer.
What a legend!