{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic5x7ktinbv3frcgya3h7kszpfzefl4k6oigurfcuk3wuddbrxgdm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3moqmrkq2kaa2"
  },
  "path": "/t/software-architecture-is-fractal-read-only-if-youre-bored/1384155?page=2#post_33",
  "publishedAt": "2026-06-20T19:37:06.000Z",
  "site": "https://community.openai.com",
  "textContent": "sergeliatko:\n\n>   1. Architecture can be captured at several levels by recursive questioning of “units”\n>\n\n\nIn this direction, I would suggest attempting to name the units by their sum function, and then have unit at the end\n\nparsers_unit\nengine_unit\nrender_unit\n\nJust that one extra definer and whatever numbers it might need if you’re using multiple like ‘units,’ would stop the drift. Simply naming all the parts as units would drag us back to?\n\nAnd looking over the whole thread, it’s kind of nice to see something we all sweat over but really don’t face head-on like this.\n\nGreat thread man!",
  "title": "Software Architecture Is Fractal (read only if you're bored)"
}