Programming

15472 readers

1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

remington@beehaw.org

alyaza@beehaw.org

Hexorg@beehaw.org

Declaration of scope (lemmy.zip)

submitted 4 weeks ago by MonkderVierte@lemmy.zip to c/programming@beehaw.org

3 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] Quexotic@beehaw.org 3 points 4 weeks ago (1 children)

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.

[–] MonkderVierte@lemmy.zip 2 points 4 weeks ago (1 children)

Yep, exactly my problem.

[–] Quexotic@beehaw.org 2 points 4 weeks 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