I once worked with a backend guy who delivered a thorough API using well-defined JSON via clear URIs.
Chris, if you're reading this, I miss you.
omg i know chris, chris rules
Liar
I'm not Chris, but this is how I backend.
Thanks, Chris
Yeah... It's extra work not to do this. Why would you make an endpoint and not throw in every property of that entity? Why would you mess with your URIs instead of making a clear division with logical entities?
Yet, somehow, most people do exactly those things.
i mean at least he documented it.
God damn where did he end up? Working for swagger or something?
Looks like he's working on healthcare web apps now
So front end does fuckall
Perfectly stable until it has a user.
the front end needs to be entirely 100% javascript with no backwards compatability, no easy deploy script, and no documentation.
We still use a bastardized mixture of soap, rest, and grapqhl with zero consistency.
I'm thankfully rid of soap. We had a few third-party services that still used it up to a couple of years ago.
Some devs had the pleasure of making contact with it on a national healthcare scale :)
Aaah, SOAP.
Yo dawg, I heard you like XML over HTTP so I put XML over HTTP in your XML over HTTP.
I've had too much raw XML parsing for one lifetime.
Pretty much why everyone just uses json or, heaven forbid, plain text for trivial data.
This whole picture:
Full Stack Developer
no no, full stack is when the entire bike is of equally dubious quality
BFF goals
I work with a lot of frontenders who always say "why would we even need backend, we can just use firebase".
Imagine if you only needed one rider though.
Scotch on the rocks is a bit strong for them
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.
