{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibx4nhlwgsx53i43ienojwudyzhd2isyx2zhdrstlggab4ekggjxi",
    "uri": "at://did:plc:b3tz6srl4ochk2wxn6dv6xpy/app.bsky.feed.post/3mhgbdvru2y22"
  },
  "path": "/Articles/1063303/",
  "publishedAt": "2026-03-19T14:19:32.000Z",
  "site": "https://lwn.net",
  "textContent": "The kernel project has a unique approach to tooling that avoids many\ncommonly used development systems that do not fit the community's scale and\nways of working.  Another way of looking at the situation is that the kernel\nproject has often under-invested in tooling, and sometimes seems bent on\ndoing things the hard way.  In recent times, though, the amount of effort\nthat has gone into development tools for the kernel has increased, with\nsome interesting results.  Recent developments in this area include the\nSashiko code-review system, a patch-review manager built into b4, and a new\nattempt at a framework for the specification and verification of kernel\nAPIs.",
  "title": "[$] Development tools: Sashiko, b4 review, and API specification"
}