Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Meaning of the tag software practices?

Parent

Meaning of the tag software practices?

+4
−1

Some new tag "software practices" just popped up, no wiki.

What's the purpose of this tag and how is it useful? What exactly in software development is not "software practices"? Seems quite superfluous and very broad.

Is it supposed to mark questions that are subjective or asking for best practice somehow?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (4 comments)
Post
+3
−0

(The user who created the tag)

The tag was to make it clear that (somewhat) opinion-based questions are allowed on site, with the [software-practices] marking which questions are about "best practices", "pros and cons", and other such questions where there is no "right" answer, but there can definitely be good answers that give reasons for or against doing things one way or another.

For example, Should I cast to (void) when I do not use the return value is marked "software-practices" because it is asking for programming practices, and the answers there provide valid reasons on whether or not to do it.

If I had the ability to edit tag descriptions, I would say something like

This tag is used for questions that ask about the benefits of using a certain style, framework, etc., possibly over others, ask about best practices, or otherwise ask about software practices. These types of questions usually ask, "Should I" or "Is it a good idea to", rather than "How", "What" or "Why".

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (5 comments)
General comments
Estela‭ wrote about 4 years ago

best-practices seems like an easier to recognize term than software-practices. I've seen the former plenty of times but the later only here.

Skipping 1 deleted comment.

Monica Cellio‭ wrote about 4 years ago

Ok, I added that as a short description for now, while the community figures out what this tag should be. We can edit, rename, or remove later, as needed.

Lundin‭ wrote about 4 years ago

If it is on-topic, then there is no reason to create a tag for this - it becomes a meta tag. It is in my opinion better to spend the effort into drafting help pages for how to ask these kind of questions.

Lundin‭ wrote about 4 years ago

As for the cast to void question, it isn't even subjective. There's industry consensus that doing so when a return value isn't used is mandatory, save for a number of old standard library functions that aren't used in that way out of tradition.

Moshi‭ wrote about 4 years ago

For some reason never got around to answering this: "As for the cast to void question, it isn't even subjective."

It is subjective as long as it isn't a completely technical question - as the standard allows it, the choice of whether or not to do it falls under best practices.