{
  "id": "p_bJP6BCRqVzK4Iafn",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_bJP6BCRqVzK4Iafn",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"GraphQL And The Human Reasons Behind Our API Patterns,\" Kin Lane, November 11, 2026, https://apievangelist.com/2026/11/11/graphql-and-the-human-reasons-behind-our-api-patterns/\n\nPriya had been a backend engineer at a logistics company for six years, and she opened the post on her phone while waiting for a build. Someone in her feed had shared it. The post said more than 32,000 people had seen the screenshot it was about, and she could see why. It was a screenshot of a screenshot, and it was funny.\n\nShe read the exchange and laughed. Then she stopped laughing, because her team had a proposal sitting in a drafts folder. It was a GraphQL layer, meant to stop the mobile team from filing requests every time they needed one more field. She had written most of it herself, and she had called it a performance improvement.\n\nReading on, she felt defensive first. The post said the pattern is rarely technical and is almost always business or politics. She thought that was a little too tidy. Her proposal had real merits. Payloads were bloated, and the mobile screens did need different shapes of the same data. But she also noticed that the strongest technical argument in the draft was a paragraph about how long the mobile team waited on her team. That paragraph was about people, and she had put it under a heading about latency.\n\nThe comments section of the post unsettled her more than the post did. One commenter's question stuck: was the problem that frontend devs don't want to talk to backend devs, or that too many of them want to talk to backend devs? She wasn't sure which one she had. She counted the requests from the mobile team in the last quarter, and most were small and repetitive. That sounded like a bottleneck. But she also remembered the Tuesday she had answered a field question with a sigh, and that sounded like something else.\n\nShe did not fully agree with the author. She thought not having to coordinate was worth a lot, and the post agreed, in the commenters it quoted. She still doubted that her situation was only politics. Some of those payloads really were too large. She decided both things could be true and that the post wasn't claiming otherwise.\n\nWhat she kept returning to was the line about the Mitch story. The post put it as \"Everyone has a Mitch.\" She tried to work out who hers was, and was uncomfortable to find that the mobile team might have one too, and that it might be her.\n\nThe post offered an alternative for a team that is a bottleneck: \"a well-described contract, good documentation and a self-service way in\". Her team had none of those. The OpenAPI file was eight months stale.\n\nShe did not delete the draft. She did not send it either. She put it aside and opened the stale OpenAPI file. The post had asked \"which human problem you actually have\", and she wanted a day of honest evidence before she answered. So she started by adding descriptions to the three endpoints the mobile team asked about most, then posted the link in their channel with a note asking what was still unclear.",
  "title": "Fiction: A reader of \"GraphQL And The Human Reasons Behind Our API Patterns\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-11T18:27:38.503Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}