Yes, the tag is helpful. I consider it to be useful in the same way beginner is useful.
reinventing-the-wheel is for when:
you are specifically trying to mimic some system/behaviour
you know that there are libraries, language features, etc. that do what you need.
you are doing it for academic reasons... to learn, not to profit.
there is no expectation that ...
I think many of the above can go, but I think these should definitely get burninated:
They really add nothing to the question, and they are already naturally ingrained in the review process. Pretty much every question is about refactoring in some way. Everyone wants their code to be clean (we're not PP&CG). Everyone ...
I feel that these are useful and should stay. Users may want to follow or ignore these tags for various reasons. For example: I'm an intermediate level code monkey, so I find if easier to answer the beginner questions.
optimization feels awfully similar to performance and should probably be a synonym.
Really, I think that the tag is really broad.
We have enough tags that we don't need one for Conditions.
(almost)All code has conditions in it for one thing or another. I really don't think that adding the conditions to any question adds any quality to the question.
Burn it, Burn it with Fire!
I've never liked the optimization tag. I would like to see it burninated and replaced by three tags:
speed-optimization, synonymized to performance
A question that asks for "optimization" in general doesn't have focus, and doesn't need any of those tags at all.
This reorganization would also pave the way for the ...
I'm going to defend all these tags, because after thinking about it, I think they do provide value.
First and foremost: .net / .net-core are not universal/compatible. Just because something works in .net does not mean it works in .net-core, and vice-versa. These tags are two completely separate frameworks, so I agree with creating a .net-core tag. Now, you ...
The reason why these tags are useful is that they affect the set of helpful review comments. The way that I interpret these tags is:
python + python-2.7 — only required to run under Python 2.7, presumably because it is interfacing with a legacy system that has not yet been ported to Python 3. Review comments about portability to Python 3 are probably ...
Yes, the naming tag should be eliminated through burnination, since it adds no value. Every piece of code (except simple assembly and esoteric languages such as brainfuck) involves naming, and every answer is free to address any issue including naming. Therefore, naming is an implied concern in every question, and the tag adds no value.
If a question is ...
Burnination would be a step too far: even if the tags aren't appropriate for these particular questions, they have a potential legitimate use. If you've written an Eclipse plug-in or a Visual Studio extension, you might want to submit it for review, and then how would you tag it?
I think this should be synonymized with conditions instead of burninating it altogether. This does still involve conditionals, the difference being is that this is about the operator. A few questions are also already tagged with conditions.
I've suggested the synonymization here.
beginner tag should stay.
It has the following benefits
it allows question askers to categorize themselves in a way that is 'easy'. It is much easier (psychologically) to admit a lack of knowledge using a tag, than to say: "I know I am making a mess of things, but I am new here, and don't know what I am really doing".
it allows reviewers to ...
Considering that Tony Hoare calls the invention of the null pointer a "billion dollar mistake", I think it's a very worthy concern for software developers, on par with exception-handling, comments, or naming. Also, the treatment of NULLs in SQL is tricky. If a developer has a question about the handling of nulls, then it wouldn't be unreasonable to tag ...
I'm not convinced that the tag should stay, because:
teaching is a meta-tag, describing the status of the question being asked, rather than the content. On Stack Overflow, they have been deprecating meta-tags. I realize that we still have meta-tags like beginner and homework, and I'm not currently pushing to eliminate them from Code Review, but I'm ...
No, do not burninate
We do need specific tags for games. See Game tag - When to create own tag for games?
Some genres of games, are popular enough that they do deserve their own tag.
For example, I am a huge fan of minesweeper, having asked several questions about it and having spent countless hours analyzing the game, I am definitely interested in that ...
Note: Given that minification doesn't actually exist, this answer will simply focus on code-size-optimization.
There are four possible logical uses of code-size-optimization:
A compiled language requires a minimal executable size, usually because it's being used in an embedded system.
A client-side web-based language needs a minimal source code size ...
[beginner] is unquestionably a meta tag, and yet, we continue to allow it to exist on Code Review.
Yes. Indubitably, it is a meta tag and as a general rule, we don't allow meta tags. However, rules are meant to be broken and beginner is special so we allow its continued existence here.
Why though? What makes this meta tag different? Mostly, it's because ...
I actually follow this tag, so I figured I would take the opportunity to chime in a bit.
I wrote a little SEDE query to find what other tags are being used along with database, besides the usual SQL and NoSQL culprits.
I have not spent that much time looking at each one individually, but apparently either some of them are mis-tagged with database, or ...
Yes, we should keep it
First up, the following issues you have pointed out can be fixed (and I am in the process of doing that):
it will have a tag wiki soon
the excerpt will be clarified to express what the tag has really been used for.
Note: I have gone ahead and corrected the above issues. Feel free to revise my suggested wiki page: view it ...
I believe architecture is especially worthy of burnination as it's specifically off-topic:
Higher-level architecture and design of software systems
The wiki even supports this:
Architecture encompasses the process, artifacts and high-level structure of a solution.
The tag also already has several closed questions. Here's one that stands out to ...
We don't need any of these tags. Not only are they meta tags, but I have no clue what they are or what they mean without going to the tag description.
How are these tags useful? How are these tags addressing something that
The asker won't already mention when asking the question
Won't be reviewed with or without the tag?
Absolutely everything about a ...
Go easy on me. Also, that complicated but unquestionably better approach you were going to suggest? Don't suggest that. Despite being objectively the only right approach, it's too complicated for me, so don't even bother putting it in your answer.
I don't quite agree with this 'code'... if anything, an answer that can simplify a 'complicated but ...
On Code Review tags are more useful when they refer to:
The features that the code on question is implementing i.e linked-list
The context that question is originated from i.e programming-challenge
The subject that question is related to i.e mathematics
A generic programming functionality that usually takes part on most applications i.e authorization
No, your statement that join is related to sql is a faulty assumption.
There are also questions about performing joins with excel, csv, pandas, or just joining data the hard way in regular programming languages.
While it is true that most interesting sql queries involve some kind of JOIN, that is not universally true. (Many INSERT and UPDATE queries do not ...
I agree with 200's answer.
All reviews should be implicitly 'teaching': teaching the OP.
In contexts where 'teaching' might be useful (e.g. "we can't use exceptions here because we haven't covered those in class yet"), that fact can be a comment (the mere presence of the 'teaching' tag doesn't convey such sufficient/accurate/useful information).
Here is ...
The selected meta tags will be burninated in phases, based on usefulness (but may still vary as decisions are made). This post will be updated as burninations are done, up until the question is tagged as status-completed.
"Blacklisted" means that a tag can no longer be created by anyone.
"→" signifies synonymization, the rightmost tag being the ...
No, form should stay.
html is a general form of web-based user interface which focuses on output from the system, and display to the user.
form focuses on user input, it is a specific subset of HTML that has a dedicated purpose that's distinctly different from other uses of HTML
I've seen many posts using database in combination with mysql, sql, oracle and postresql.
If database is used in combination with multiple other database tags, it's superfluous. I've started removing the obvious superfluous ones, since they don't add any relevant information.
It's like putting oop on every c#, or iteration on anything with a for loop. ...
The database should not be eliminated. There are database-related questions beyond just SQL and variants of it. Examples:
Looking up the name and event for a ticket
Building a simple database in Python
Auto-expire key/value database (with different ...