- 1 year
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.
- 1 year
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.
- 1 year
I was going to say it handles steering and braking, but… Where are the brakes? This must be one of those bikes where you back pedal to brake, so I guess front end just steers.
- anomnom@sh.itjust.worksEnglish1 year
Steering is what keeps bikes upright though, and the longer and heavier the bike the more work it is.
Full disclosure. I used to be a front-end, then full stack dev.
- 1 year
the front end needs to be entirely 100% javascript with no backwards compatability, no easy deploy script, and no documentation.
- Olgratin_Magmatoe@slrpnk.netEnglish1 year
We still use a bastardized mixture of soap, rest, and grapqhl with zero consistency.
- wreleven@lemmy.caEnglish1 year
I’m thankfully rid of soap. We had a few third-party services that still used it up to a couple of years ago.
- 1 year
Some devs had the pleasure of making contact with it on a national healthcare scale :)
- 1 year
Aaah, SOAP.
Yo dawg, I heard you like XML over HTTP so I put XML over HTTP in your XML over HTTP.
- 1 year
Pretty much why everyone just uses json or, heaven forbid, plain text for trivial data.
no no, full stack is when the entire bike is of equally dubious quality
- 1 year
I work with a lot of frontenders who always say “why would we even need backend, we can just use firebase”.
