Per the recent discussions at What's the point of the tag [programming]? the consensus on the programming tag is that we'll keep it, but heavily re-scope it to try and focus more on theoretical and process-oriented topics.
To that end, I'd like to create some tag synonyms, but I don't believe that "programming" is appropriate as the target of those synonyms, because I don't think it helps convey the new, narrower scope.
What should we call the target of "programming?"
We should call it software-engineering; fundamentally the scope of the tag is similar to that of the Software Engineering SE: methods and practices of building software (games, specifically), including the theoretical.
software-engineering tag, it seems quite different from what programming currently covers...
\$\endgroup\$
programming as an alias. In my experience with students and recent grads, I don't think anyone has asked me about becoming a "software-engineer" as opposed to a "programmer". So I expect, while they may mean software-engineering, they're more likely to use the programming tag and not find software-engineering with out that alias.
\$\endgroup\$
We should call it programming-theory, as originally suggested. It is succinct, and not terribly dissimilar from the current programming tag, so users will be less surprised by the tag system replacing it for them when they type programming.
This mega post contains all the questions that have the tag software-engineering. Since the merge of the tag programming, some of these don't really need the tag software-engineering as the scope is different, so all of these questions tags should be revised.
The idea is that whenever you have time to review a couple of them, review them (either retag the questions or leave them as is, as needed), and then remove the questions from this list.
Once all the questions have been reviewed, we'll be able to delete this post.
???