4 ms·
Strong disagree. GraphQL has given our dev teams huge leverage. It's similar to writing a page of HTML rather than the equivalent GUI code. That might not look
by hirundo 5y ago
Strong disagree. GraphQL has given our dev teams huge leverage. It's similar to writing a page of HTML rather than the equivalent GUI code. That might not look helpful if you're already a GUI master, but it's a big productivity win for a mixed team of designers and coders. A vague query specification that used to take a week to turn around has now become a precise query specification that we can turn around in under 250ms.
- pastrami_panda 5y agoDid you try to figure out why your specifications were vague, or why implementing a query and bringing it to production took several days? Adding another dependency and attack vector before addressing the root cause doesn't sound that healthy.
- hirundo 5y agoThe specifications were vague because they were in prose, rather than a formal specification language, and written in an IDE with instant feedback, auto-complete, history and documentation. It took several days to turn around because it took a developer a half day to write the controller code and specs, to debug it, to write the PR and get it approved, to merge the branch and wait for it to be deployed. This half a day was interleaved with a full schedule as available, so routinely took a week. With a formal, executable specification that is a GraphQL query, all of the above goes away. The back-end devs don't even knows about it unless there's a problem.