{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifxj3wtk2tgq6cz7xj3s4qjqloenjqqabvcj3xfnwoptyx72tdvbm",
    "uri": "at://did:plc:2gbt2dlwaqovtnmxkat3tyke/app.bsky.feed.post/3mjy36y6fshh2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreich6fszetspgzu4lcqkx77opuw56b556uyogmq3xuv3etcg4erirq"
    },
    "mimeType": "image/jpeg",
    "size": 90144
  },
  "path": "/articles/d41586-026-01261-w",
  "publishedAt": "2026-04-21T03:48:30.317Z",
  "site": "https://www.nature.com",
  "tags": [
    "doi:10.1038/d41586-026-01261-w"
  ],
  "textContent": "Nature, Published online: 20 April 2026; doi:10.1038/d41586-026-01261-w\n\nComputer scientists share their advice for ensuring that your scientific software does what it’s supposed to do.",
  "title": "Got bugs? Here’s how to catch the errors in your scientific software",
  "updatedAt": "2026-04-20T00:00:00.000Z"
}