{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicjdimuetsdjsvsyl5pnc7mzoy3nqcet3pi2lqxf5wm7fszl3qzyy",
    "uri": "at://did:plc:chkrm663c45x2s5jupaqxvs3/app.bsky.feed.post/3mjdvrf72jgq2"
  },
  "path": "/contribute-what-you-use/",
  "publishedAt": "2026-04-12T00:00:00.000Z",
  "site": "https://avelino.run",
  "textContent": "There's a pattern I see constantly in open source contributions, and it costs everyone involved more than it should.\n\nSomeone finds a project. They like the idea. They read the README, skim the codebase, spot what looks like a gap, and open a pull request. The code is clean. The intention is good. The problem: they've never actually used the software.\n\nThe PR sits in review for a week. The maintainer tries to understand the motivation. Questions get asked. Answers are vague. The proposed solution works for a case the contributor imagined but doesn't account for how real users interact with the system. Eventually the PR gets closed - politely, if the maintainer has the energy for it.",
  "title": "Contribute What You Use: Why Real Usage Makes Better Open Source Contributions"
}