Toughest job as a web developer is to remember the status codes.

Quite easy:
100, 102, 103, 200, 201, 202, 203, 204, 205, 206, 207, 208, 300, 301, 302, 303, 304, 305, 306, 307, 308, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 426, 428, 429, 431, 451, 500, 501, 502, 503, 504, 505, 506, 507, 508, 510, 511

Did you forget to add the joke tag?

@asgs I think he did, status codes are easy

I even used 418 yesterday!

If that counts already as tough job among web devs, that would explain A LOT. I mean, a drilled monkey could easily do that.

@Root was there a legitimate teapot at the end of that?

@C0D4 😅

It's for when the client is being silly. I responded with 418 "We're all a little mad here"

Easy
100s - go on
200s - all ok
300s - not heren go somewhere else
400s - you screwed up
500s - i screwed up
🙂

I don't really know what to think of this rant.

My first thought was "why are you learning the status codes, after all they have names?" But learning a list of names vs a list of numbers is not much of a difference, so it's back to square one.

Then I thought, actually why learn all of them in the first place? There's a nice list on Wikipedia and the libraries I know have enums for that.

And finally, isn't the toughest job as a web dev that your JS library of choice will be obsolete the following week or so? And the exploded whale guts of a tool set around those, like that blog post from a couple of years ago - https://hackernoon.com/how-it-feels... - demonstrated?

So... dunno. Weird rant.

@arekxv you must be part of the HTTP WG :-D