{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibkbjs6j74zjxn5tyze2kjenxlatks636j2lwtx5jtoynxnj2cfi4",
    "uri": "at://did:plc:c4uo5im4kb23i76qndr43xi2/app.bsky.feed.post/3mm6t57ydjg42"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiaxpjzlraobcxijf52qaddgndpzbprm5mo4auarq25dt3arxwjzgu"
    },
    "mimeType": "image/png; charset=UTF-8",
    "size": 765361
  },
  "path": "/links/software-is-problem-ownership-1",
  "publishedAt": "2026-05-18T04:00:00.000Z",
  "site": "https://jonathanstephens.us",
  "tags": [
    "Generative Ai",
    "Problem Solving",
    "Solutioning",
    "Software Development",
    "Portfolio Of Problems",
    "Problem Domain",
    "Complexity",
    "Commodity",
    "Utility"
  ],
  "textContent": "> This is great for a lot of specific problems that need specific solutions that wouldn’t normally get solved easily. This has been the evergreen promise of computers and programming and hacking. But there’s a difference between solving your specific problem, and owning a problem domain.\n>  Paying for software isn’t paying for a solution. It’s paying for someone else to own a problem.\n>\n> It’s paying for someone who has the taste and the context to think through the details. For the operations and structures necessary to scale it, maintain it, and solve even bigger things.1 For the relationships that connect and abstract and expand upon the problem in ways that they can’t do, because they own the specific solution, not the whole problem.",
  "title": "What, then, are we paying for?"
}