{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigpekpkz3zm7m7zau5mkwym34izvh5fir2gjby73ujlonzqxgrfte",
    "uri": "at://did:plc:ornsbtmaufp6dx4zecjdtoon/app.bsky.feed.post/3mo7yczxaawc2"
  },
  "path": "/post/26858671",
  "publishedAt": "2026-06-13T15:21:29.000Z",
  "site": "https://beehaw.org",
  "tags": [
    "Programming",
    "MonkderVierte",
    "3 comments",
    "lemmy.zip/post/66082776"
  ],
  "textContent": "submitted by MonkderVierte to programming\n4 points | 3 comments\n\ncross-posted from: lemmy.zip/post/66082776\n\n> I never see in public git projects something like a _declaration of scope_. There’s also no convention, unlike a README.md (which rarely contains some sort of scope definition) or LICENSE file.\n>\n> Is this unusual in open source projects, that you _first_ define what you want and not want in your project and how you want to do it, to combat scope creep and sabotaging yourself?\n>\n> I’m in a postition in live (short of a burnout) where it’s actively a pain to just start things and then wing it; i even add a scope comment to larger shell scripts.\n>  Maybe it’s experience, because i already know that i’m then not satisfied afterward or (in case of shell scripts) just create a unfinished mess. Nobody else?",
  "title": "Declaration of scope"
}