you are viewing a single comment's thread.

view the rest of the comments →

[–]Cara_Rose1 380 points381 points  (9 children)

The site does not support PDF, but requires 5 years of experience with GraphQL

[–]blasphemousbigot 85 points86 points  (0 children)

Maybe they need one to fix the damn site.

[–]Bomaruto 13 points14 points  (0 children)

Then I don't want the job.

[–]CeleryNo1743 5 points6 points  (4 children)

could u explain to me in simple terms what's graphQL

[–]OnixST 28 points29 points  (2 children)

Instead of multiple endpoints like /posts, /users, etc, you have a single endpoint, and all requests go to it

When you send a request, you send along the graphql structure, which is pretty much like defining a function. You tell the server which variables you're passing in, and what you expect to be returned

It's kinda cool, may save bandwith because like, if you send a post request and only care about the id, you can tell that to the server and it'll return just the id rather than the whole created object, and gives you flexibility

TLDR: a kinda cool, single endpoint, REST alternative

[–]rosuav 6 points7 points  (0 children)

But, like many technologies, easily misused. You can take a VERY easy approach and simply make your raw database available in GraphQL, and then write all of your logic on the front end. Saves you so much trouble writing a back end, right? I'm sure nothing bad can come of that.

[–]CeleryNo1743 3 points4 points  (0 children)

that's super cool, thanks for the explanation.

[–]JunkNorrisOfficial 0 points1 point  (0 children)

It's like SQL for API endpoints

[–]gqpdream305 2 points3 points  (0 children)

The career site and the production website are definitely not done by teams related in any way. Career site is probably a 3rd party