Maybe not exactly what would happen, but not wrong either. At the end of the day, these two fields are different.

I've seen all sorts of people doing all sorts of stupid stuff. Fresh example - backenders (supposedly), upon a wrong request, still return 200, but with empty response body. Go figure...

I think frontenders don’t usually come up with the design (as the joke suggests). They just implement what designers come up with. They are not that different from backenders.

@kamen yea not so long ago I got an eye roll when I asked the guy on backend to return the correct status codes. This is the same guy who won dev of the year

@TheBeardedOne I’ve heard one good argument for this: the mobile dev contractor who was using endpoints built by API Guy (in #hell / the printer place I worked at previously) was getting 404s and couldn’t tell if he was using them incorrectly or if they weren’t built yet. API Guy insisted they were finished; they were not. They didn’t exist, and thus returned 404s.

Insisting that API Guy instead return 200 {status: “error”} removed the ambiguity.

@Root

That's still on API guy.

Bad requests return 400, not 404.

I've seen far worse frontends.