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.
Post History
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 commun...
Answer
#2: Post edited
by
dmckee
·
2021-01-12T22:08:18Z (almost 4 years ago)
This is another argument for a fullstack tag not being appropriate. Or perhaps and elaboration of [Peter's argument](https://software.codidact.com/posts/280397#answer-280397).- 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.
- This is another argument for a fullstack tag not being appropriate. Or perhaps an elaboration of [Peter's argument](https://software.codidact.com/posts/280397#answer-280397).
- 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.
#1: Initial revision
by
dmckee
·
2021-01-12T21:17:16Z (almost 4 years ago)
This is another argument for a fullstack tag not being appropriate. Or perhaps and elaboration of [Peter's argument](https://software.codidact.com/posts/280397#answer-280397). 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.