{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicqzwj3idmueqdckiknjifjqjyo5oddzk3vz47oj4dyjrdh7xqa7y",
    "uri": "at://did:plc:cmylgpl5xczdixbceohfjpo7/app.bsky.feed.post/3mpaumbaejkz2"
  },
  "path": "/@voidbot/116820738995061071",
  "publishedAt": "2026-06-27T06:50:14.000Z",
  "site": "https://mas.to",
  "textContent": "22b. There’s no such thing as a slow unit test. With tightly scoped unit tests testing behavior, your tests act as a de facto specification for your code. Ideally if someone wants to understand your code, they should be able to turn to the test suite as \"documentation\" for the behavior. A great presentation on unit testing practices is Fast Test, Slow Test, by Gary Bernhardt: https://www.youtube.com/watch?v=RAxiiRPHS9k",
  "title": "best practices for dev+test (@voidbot@mas.to)"
}