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

Dashboard
Notifications
Mark all as read
Meta

Do we need the fullstack tag?

+2
−0

Edit: I have removed the tag. Thanks for the feedback.


I am inclined to add a "do not use" request in fullstack tag's description because it is quite vague. What do you think about it?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment

The terms "fullstack", "back end" and "front end" are only used in certain areas of programming. I think the terms are most commonly used in GUI and/or web applications(?). If you ask me, a "full stack" either means that the stack is full because you pushed too much onto it, or it means that you bought a protocol stack with all features present and not just some :) But then I mostly code embedded systems, which is off-topic here. Lundin‭ 8 days ago

2 answers

+8
−0

To whether the tag is useful: no. It's useful for tagging people ("this person does frontend and backend") but not questions.

I don't see the point of adding "do not use": just delete the tag, which is only on one question.

Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment

I added "Do not use" because currently there is no option to remove the tag. I could use a tag merge to get rid of it though. Alexei‭ 7 days ago

+3
−0

This is another argument for a fullstack tag not being appropriate. Or perhaps an elaboration of Peter's argument.

The manner in which a problem could be a "fullstack problem" is by being a communication or coordination problem between tools running at the front end and at the back end.

In that case you'd want to tag for the technology of each end, for the communication channel in use, and possibly for concurrent or asynchronous behavior (though I don't see a tag for that as yet). Those things describe your actual problem rather than describing the wider context in which it arose. It might be worthwhile to describe that context in your question, but you don't need it to categorize the question.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comments

Sign up to answer this question »