{
  "blyg": "0.3",
  "id": "4ppx0ne1j6sb55zvsmqxxbkj8s",
  "kind": "fragment",
  "origin": "https://www.msweet.net/notes/",
  "page": "586-plum-geese",
  "author": {
    "name": "Matthew McDowell-Sweet",
    "url": "https://www.msweet.net/"
  },
  "created": "2026-11-17T22:13:25Z",
  "updated": "2026-11-17T22:13:25Z",
  "version": 1,
  "content_md": "Fun list to orientate around.q\n\n> A big part of a staff engineer’s job in a platform team is to figure out what the team should build next - I like to call that “inventing work”. Thankfully, the signals that help us to invent work are already out there, and they arrive from four directions - from the systems, from the users, from your organization, and from the industry. What follows is a guide to reading each of them.\n\n[A Staff Engineer's Guide to Inventing Work - Sujith Jay Nair ↗](https://sujithjay.com/inventing-work)",
  "content_html": "<p>Fun list to orientate around.q</p>\n<blockquote><p>A big part of a staff engineer’s job in a platform team is to figure out what the team should build next - I like to call that “inventing work”. Thankfully, the signals that help us to invent work are already out there, and they arrive from four directions - from the systems, from the users, from your organization, and from the industry. What follows is a guide to reading each of them.</p></blockquote>\n<p class=\"source\"><a href=\"https://sujithjay.com/inventing-work\">A Staff Engineer's Guide to Inventing Work - Sujith Jay Nair ↗</a></p>",
  "content_hash": "sha256:80c8dcf08d48ea159fb62ea4f9c1dcef1665888029ac62e2932e3d4533a3d7ba",
  "media": [],
  "changelog": [
    {
      "version": 1,
      "at": "2026-11-17T22:13:25Z",
      "note": null
    }
  ]
}
