{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2024-09-14T03:51:00Z",
      "note": "Imported from the Ctrl+Shift archive",
      "version": 1
    }
  ],
  "content_hash": "sha256:ec2013a5902d8762069de61808882174592bbb69f2ef5e87e3b268f2f4fb1f04",
  "content_html": "\u003ch1\u003eAspire, but act your scale\u003c/h1\u003e\n\u003cp\u003eOver on the technical side of the fence, the go-to thing to poke fun at in terms of overkill decisions these days is “you probably don’t need Kubernetes”. There’s a lot of these: “your data isn’t Big Data” and “your blog needn’t be a SPA” and so on.\u003c/p\u003e\n\u003cp\u003eThese tools aren’t without their use! They exist because some people and orgs truly needed them, and built or sought them until they were brought into existence. None of those places, however, brought those tools into being solely because it was the default approach for Serious Companies that do Serious Things.\u003c/p\u003e\n\u003cp\u003eAnd when other people and orgs with simpler needs implement these tools aspirationally, it’s often rightly pointed out that they’re using a fusion cutter to slice bread: it’s shiny and sparkly, but expensive, overcomplicated, and may not even do as good a job.\u003c/p\u003e\n\u003cp\u003eYet when it comes to management, we often forget this wisdom.\u003c/p\u003e\n\u003cp\u003eIf you have a department with a dozen people in it, you probably don’t need matrix management.\nIf everyone in your organization knows each other by name and face, you probably don’t need deeply-tiered OKRs.\nIf your org sells gimmick t-shirts, you probably don’t need a dedicated sales department.\u003c/p\u003e\n\u003cp\u003eBut the temptation remains to use the tools that bigger, more complex places have come up with—for sheer interest, for aspiration, for résumé padding.\u003c/p\u003e\n\u003cp\u003eWhat tools and frameworks are you using in your work? Are they there to support the node level of your hierarchy in doing their best work? Or are they there for Another Reason?\u003c/p\u003e\n",
  "content_md": "# Aspire, but act your scale\n\nOver on the technical side of the fence, the go-to thing to poke fun at in terms of overkill decisions these days is “you probably don’t need Kubernetes”. There’s a lot of these: “your data isn’t Big Data” and “your blog needn’t be a SPA” and so on.\n\nThese tools aren’t without their use! They exist because some people and orgs truly needed them, and built or sought them until they were brought into existence. None of those places, however, brought those tools into being solely because it was the default approach for Serious Companies that do Serious Things.\n\nAnd when other people and orgs with simpler needs implement these tools aspirationally, it’s often rightly pointed out that they’re using a fusion cutter to slice bread: it’s shiny and sparkly, but expensive, overcomplicated, and may not even do as good a job.\n\nYet when it comes to management, we often forget this wisdom.\n\nIf you have a department with a dozen people in it, you probably don’t need matrix management.\nIf everyone in your organization knows each other by name and face, you probably don’t need deeply-tiered OKRs.\nIf your org sells gimmick t-shirts, you probably don’t need a dedicated sales department.\n\nBut the temptation remains to use the tools that bigger, more complex places have come up with—for sheer interest, for aspiration, for résumé padding.\n\nWhat tools and frameworks are you using in your work? Are they there to support the node level of your hierarchy in doing their best work? Or are they there for Another Reason?",
  "created": "2024-09-14T03:51:00Z",
  "id": "7bct2phra45pbpd6xr702krzzb",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/aspire-but-act-your-scale/",
  "transclusions": [],
  "updated": "2024-09-14T03:51:00Z",
  "version": 1
}