Hot answers tagged

19

I personally quite like that "warning", it inspires you to create titles that are more imaginative than "FizzBuzz from a file" - how about "IFSFB - Input File Specified FizzBuzz" Do something different, something that will stand out. The alternative will be thousands of questions called: "Singly Linked List", or "FizzBuzz", or "Project Euler #13" If we ...


19

It's true that language in a title should be avoided whenever possible. There is another obstacle though that we need to deal with. Given the way Code Review works, there are essentially no duplicates. We tell you what you need to know, even if you've done the same "mistakes" as some others before you. So this inevitably leads to a lot of "Noughts and ...


18

A pun is only a pun if it relates to something meaningful. Something like: "The trip to the arctic was so cool" is only funny because there's two meanings to the word. The same has to be true with a punny title. The title has to have relevance to the question at hand, but, if you can make a pun out of it, and the "other" meaning is entertaining, then sure, ...


17

It seemed like a good idea at the time (Prompt for more meaningful question titles). However, it seems like either People have a hard time trying to satisfy both requirements, and/or Some people just won't read instructions no matter what. I propose that we try a new prompt: State the task that your code accomplishes. Make your title distinctive.


16

We usually VTC questions with titles that don't reflect the goal of the code. I find this entire premise very, very, very sad and completely contrary to the very welcoming spirit that made this site a success. A bad title is just that: a bad title. It does not take away anything from the post, it does not make a question off-topic in itself. Code isn't ...


15

Yes, please help bring any post that you find up to standards, as if they were posted today. Old posts do resurface in unexpected ways — for example, as you have observed, they may be recommended as related posts — and their presence may set a bad example. By the Broken Window Theory, any bad example will likely inspire more posts of lower quality.


14

If the programming language is not integrated into the title, something like: C++ - Reading n chars from stream to string [C++] Reading n chars from stream to string C++ Reading n chars from stream to string Reading n chars from stream to string - C++ then all it does is to act as a something like tag. And that's what actual tags are for, so you should ...


14

Let me know if I am allowed to do this You're allowed to do this, and it has been done before. However, it's not a particularly good idea with regards to question clarity and quality. This is one of those cases where if you can do it better, you probably should do it better. Examples that such a scheme has been done before: JSON Test Harness: Part 1 JSON ...


13

Yeah, this probably should've been done long before now - it's clear this has become a persistent problem here. Starting now, the following words/phrases are not allowed in titles: "review" "critique" "improve" "help with" "question" (unless followed by "mark") any sentence starting or ending with "help" or "problem" I can't do much about the mess that'...


13

Regularity in the “Rusty Towel of Mutual understanding” Author: Rolfl (revision 3) | answered This question also went to the Hot Network Questions and into the weekly CR newsletter the week it was posted. I think this was a great title because it's not only eye-catching and intriguing, it actually - believe it or not - says exactly what the post is about, ...


11

Thanks for taking the initiative to help improve question quality. I see a few problems with this idea, though: If you automate any edits, please do so in a way that doesn't flood the front page. You'll need to rate-limit the changes. If the title is bad, it is likely that other things need to be improved with the post as well. Ideally, you should make ...


11

Creating different titles for follow-ups is difficult, so most follow-up questions tend to have very similar titles which is perfectly fine. Some options for naming a follow-up question is: XYZ Program v2 Follow-up to XYZ Program XYZ Program continued XYZ Program - follow-up If you want to be creative, you can try to be creative with your titles for the ...


10

Questions have four types of visible metadata that can be used to distinguish them from one another: The title, which is the first thing one sees of the question. In some lists, this is the only identification for a question. The tags, which allow filtering The excerpt, which is mostly useless The user card, which is usually some subset of {name, picture, ...


10

It is often said that you should use the right tool for the job. What is the right tool to determine if a question is on-topic or off-topic? I certainly believe that it is not blacklisting titles. I already had some minor problems when "Review" was blacklisted so I changed the title of one of my questions to use "CR" instead. Though I still can live with ...


10

I think that as long as these titles reflect what the code does to a certain extent, it should be fine. To go with your examples : "Hooked on Windows" : It's not that clear. The pun's there, that's fine, but the message is a little more hidden IMO. "Go on, mock my IDE" : Considering the tags and the title, I can figure it's about mocking, which makes it ...


9

In a way, I don't think it's possible to specify a "site-policy" about this. It is up to each user to post comments as they wish, and up to each user to improve their comments as they wish. This one comes directly from a collection of Frequently Posted Comments for users of the Auto-Comments script, as such it is several users that already uses the comment. ...


9

The following posts contain 'syntax' in the title: https://codereview.stackexchange.com/search?q=title%3Asyntax there are 19 of them. None of them are concerned about syntax errors. "Error handling" is the most common pair when searching for 'error' in the title: https://codereview.stackexchange.com/search?q=title%3Aerror I can't see where 'syntax' is ...


9

It's not really rude as such — you don't speak down to or insult the person — but I think it could be improved. When you're trying to correct a behavior, it's important to explain: What the person did that's wrong; Why the behavior is wrong; What they can do to correct the behavior. Your comment only touches on the third point, so without ...


9

The point with CR (again - IMnsHO) is rather to present a proper, readable and maintainable coding style. This is where we might disagree. The point of Code Review Stack Exchange is to ask for reviews, it is not about the final result, but about the process. Code Review Stack Exchange is not a repository where we have a whole bunch of working programs, in ...


9

Getting the best value out of Code Review I disagree with the premise that Code Review is about "Whatever your XXX, apply YYY". Code Review looks at your code, holistically and in the context of its intended usage, and provides customized advice to improve your program and your coding skills. As the Help Center states, Code Review is not the place to ask "...


9

Should these titles be edited to summarise the problem statement? Yes. Peilonrayz has already quoted the relevant text here, but came IMO to the wrong conclusion. The relevant FAQ talks about a proper suggestion of a similar title that contains the following: <Challenge platform> #<i> - <Name of challenge> It's not the best way of ...


8

I like amon's answer a lot here, but I wanted to contribute with some extra suggestions What actions [are we taking|can be taken] to avoid, in the long run, titles like "Simple Calculator Implementation #429"? If it is a common implementation (Linked List Implementation, Fizz-Buss, some kind of Calculator), focus on what makes your implementation stand ...


8

KISS my... unit of work Author: Mat's Mug (OP) This question went to the Hot Network Questions and into the weekly CR newsletter the week it was posted. I think it was a great title because there's a touch of humor, and it still conveys what the post is about and what the OP's main concern is.


7

Questions on meta marked with "obsolete" in the title are there for historical reasons only. There were times when certain policies and procedures were introduced to streamline the use of Code Review as a site, and, after that, a new, better policy was introduced making the old one obsolete. Where questions are marked as obsolete they also have a link to ...


7

We can do better. It is possible to write a title that is both informative and punny. Compare these two titles: (Original) Hangman my logic compared to others (New) A different way to execute a hangman game Now, this wasn't my question, but it had a boring, awkward title (the first bullet). So I suggested a better one. Now, I did remove some information (...


6

I have no problems with [feedback, reviews, etc] in the title as long as it accompanies the type of program in some form. For instance, I'm okay with this: Cleaning code in binary tree structure ...as opposed to this: Cleaning code in this program While they both accomplish these things: You know right away that the question IS on-topic If you're not ...


6

I've just made this change, actually a bit surprised that it took this long to be noticed. Sorry about the delay in our response, this is now live.


6

I don't think your comment is rude. That being said if you wanted to soften it a bit and be more explicit about the "call to action" for the user, you could word it along these lines: Welcome to Code Review! Your question title in its current form is ambiguous. Because we want to better understand your question so we can review it, please consider ...


6

If she floats then she is not a witch like we thought Author: syb0rg


Only top voted, non community-wiki answers of a minimum length are eligible