this post was submitted on 14 Sep 2025
779 points (99.6% liked)

Programmer Humor

27117 readers
2460 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
779
REST my ass ๐Ÿ’ฉ (eviltoast.org)
submitted 1 month ago by orhtej2@eviltoast.org to c/programmer_humor@programming.dev
101 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] jj4211@lemmy.world 1 points 1 month ago

misdiagnosing errors originating from transport as application errors, and vice versa.

Shouldn't the response body disambiguaite clearly whose fault it is? I mean you have to anyway if you advocate for '200 for everything'. You still have that same response body whether the HTTP status code is 200 or 500.

We honor the status code while providing an error body and it's always blatantly obvious whether it's an infrastructure issue or "true backend" issue when we see an issue. In my team I can't recall anyone ever getting confused for even a little bit about whether an observed anomaly was web infrastructure or the backend, despite us setting HTTP status codes to error when, you know, we see an error.