Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Lensflare8561242dI was waiting for this answer 😆
magicMirror10271242dFuckkkk Gql. Srsly.
Returning 200 ok and wrapping the actual 50? error?
Fuck it with a sideways cactus.
Lensflare8561242d@magicMirror this has nothing to do with graphql. People do this shit with REST, too.
magicMirror10271241d@Lensflare That reminds me:
Fuckkkk idiot devs.
Avimelekh156241dOh I know the pain when people who barely can wrap their head around rest start pushing GraphQL for fucking everything. There will be special place in hell. My personal pain and suffering i deal every day some ingenious guy thought we should bring down db connections for accessing data, which itself is good idea, by implementing graphql proxying now instead on http1.x cause fuck reasoning.
ostream3863241d@magicMirror We would return the proper error code, GraphQL is for the body and sits on the top of HTTP.
Honestly, it's kinda neat, I almost never needed to cross data, ad-hoc request, and so on
Linux17Moving a datacenter, it went bad. The upstream ISP fucked us. 45 hours. I drove home, it was the most dangerou...
aviophile6I don’t work without rest. In fact, I rest during the work. I was once got caught by the director(3 level ab...
rov3rand0m1Longest I worked without rest: about 13 hours Why: first job + young and stupid
About two years
We were using graphQL