Programming

27279 readers

154 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Declaration of scope (lemmy.zip)

submitted 2 days ago* (last edited 2 days ago) by MonkderVierte@lemmy.zip to c/programming@programming.dev

12 comments fedilink hide all child comments

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? Or am i looking for the wrong term?

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

[–] trem@lemmy.blahaj.zone 6 points 1 day ago

Might also be a product of experience, that you have a need for strict scope definitions.

When I was unexperienced, I would actively look for projects I could do and features to add to them. Because well, most project ideas were too large for me to tackle anyways and I needed the experience.

Now that I have experience, I have multiple long-term projects that could use some love, if I find the time. And I have the experience to tackle virtually any project idea, if I find the time.

Don't particularly want to add another long-term project into the rotation, so I do spend a lot more time thinking upfront "when will this be finished?".