Spyke
lemmy.world

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.

125

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.

5
mesareply
piefed.social

God damn where did he end up? Working for swagger or something?

2

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.

2

the front end needs to be entirely 100% javascript with no backwards compatability, no easy deploy script, and no documentation.

28
wrelevenreply
lemmy.ca

I'm thankfully rid of soap. We had a few third-party services that still used it up to a couple of years ago.

9

Some devs had the pleasure of making contact with it on a national healthcare scale :)

5
lemmy.nz

Aaah, SOAP.

Yo dawg, I heard you like XML over HTTP so I put XML over HTTP in your XML over HTTP.

4

Pretty much why everyone just uses json or, heaven forbid, plain text for trivial data.

2

I work with a lot of frontenders who always say "why would we even need backend, we can just use firebase".

6
lemmy.ca

False. Front end needs to be an entire gaggle of shit and duct tape, all covered in shiny aluminium foil.

3

You reached the end

Backend 🤝 Frontend | Spyke