cross-posted from: https://lemmy.zip/post/66082776

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.

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?

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.
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?

  • ɔiƚoxɘup@beehaw.orgEnglish
    3·
    15 days ago

    I think I like this idea. It sets a clear landmark for “done” and resists the inclination I have to make perfect the enemy of good.

      • ɔiƚoxɘup@beehaw.orgEnglish
        2·
        15 days ago

        Downside being, it would force me to be disciplined and not keep adding bits and bobs onto scripts and instead build stuff into useful modules and libraries and things. Ugh. Lol