Should I make a post in Meta to ask guidance for the usage of the tags without usage guidance that I'm considering to use in my next question before posting it?
Tags are part of the core elements of the Stack Exchange model. Questions should have at least one tag. Each tag has a tag wiki, showing tag stats, amogn other automatic content and two community editable parts,
- Usage Guidance also known as excerpt and usually referred as tag excerpt. This content is plain text and limited to 500 characters.
- tag body, usually referred as tag wiki. This content is rich text, and could be a lot longer that the tag excerpt
On some SE sites besides the brief usage guidance provided on the tag excerpt, the tag body is used to include an extended usage guidance.
As new user in this community, I'm a interested on learning its workings. This post is about properly use of certain tags that I have found multiple interesting for me that doesn't have usage guidance, some has conent in the tag excerpt but most of them don't include a extended usage guidance in the tag body.
So far I only found one tag with usage guidance in the wiki, development-environment, apparently derived from the efforts around Analysis of the [development-environment] tag. I have seen that there are some Meta post labeled "Structured Tag Cleanup", created 5 years ago. Also I have seen posse but this tag hasn't a tag excerpt / tag body.
This is a follow-up question derived from Is "citizen development" on topic in Software Engineering?. The tour and some tags mentions that community members education is important on this site, I'm a self-learner of Software Engineering that have read stuff about the unified process, UML, Martin Fowler's Analysis Patterns books and some work expefience very close to this field. Based on this I took terms that I think that might be related to Citizen Development that might be on-topic in this site. Below there is a partial list of the tags that I have reviewed that has a tag wiki excerpt. Most of them haven't usage guidance.
Tags having "explicit" usage guidance
Questions about problem solving and planning for a solution through software design.
Questions about the environment in which software development happens. This includes the hardware, software, and processes and methodologies used. Questions are expected to be unique to software development and require the expertise of people with education or experience in the field of software development.
For questions relating to the process of developing software.
For questions SPECIFICALLY related to development within an enterprise environment (e.g. a large company), as opposed to e.g. hobby programming. Don't use this tag just because you're working as an enterprise developer.
Tags that describe the concept. Could work as usage guidance.
Application design covers the entire pre-implementation phase of a project and consists in conceptualizing the architecture, its components, the interactions between each component, the data flows, and the processes to implement.
services provided on-demand and easily scale up and down
Configuration is an arrangement of functional units according to their nature, number, and chief characteristics.
Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional and physical attributes with its requirements, design and operational information throughout its life.
A domain model is composed of the objects, behavior, relationships, and attributes that make up the industry that is the focus of development.
The high level design and description of software systems frequently characterized by having large quantities of persistent data that is accessed concurrently.
According to Wikipedia, knowledge transfer is the practical problem of transferring knowledge from one part of the organization to another.
Creating and manipulating abstract representations of a problem or of software elements for the purpose of facilitating the understanding, reasoning, and solving of the problem.
Programming Practices are the commonly or not so commonly used practices in development of software. These can include things like Agile Development, Kanban, Coding shortcuts, etc.
Programmers working alone, both on personal projects and on contracts.