Skip to main content
added 1074 characters in body
Source Link
Daniel Daranas
  • 4.1k
  • 1
  • 22
  • 40

The original is a bad question and should be closed, and this is a bad question because it has encouraged bad answers which, influenced by the original bad question, do notfail to focus in the essentially trivial algorithmits essential parts.

The original is a bad question

The OP of the original question did a terrible job in clarifying requirements. When you are trying to solve an algorithm you need to focus on the important ideas and not be distracted by data which may be related in the real world, but totally unrelated to the particular algorithm.

Croissants are such data. Not only their picture, but their very mention distracted everyone. It would be ok if the question had been otherwise clear, i.e. if besides the useless picture the requirements had been clearly isolated. But they were not.

In my opinion this question would only fit in a Stack Exchange site which does not exist yet: Requirements Definition (or perhaps Problem Definition). People (mainly non-programmers) would post their everyday problems there (Which bus stop should I choose if...? How many elevators do I need if...?) and the answers would clarify the exact requirements for them.

In our example, people would set to ask the OP if it's ok that someone brings the croissants twice in a row, or three times in a week, just by chance, as a result of the randomness. And two or three more questions specific to his problem. Then they would clarify the problem in a set of basic requirements, which would be the answer.

It would be a bad Q&A site, because it would be one in which people do your work for you and virtually noone else can benefit from it. In any case, it wouldn't be StackOverflow.

This is a bad question

The original should have been closed as off-topic because it doesn't show a minimal research effort and it doesn't demonstrate a minimal understanding of the problem being solved. It basically asks for a minimal understanding of that problem, as I said before.

This question dedicates a special attention to the original one, as if it was "special" in some way. As if it should generate a debate about lots of upvotes, nice images, popular title, popularity and close reasons altogether. It shouldn't. Each of these subjects should be (and has already) discussed independently on Meta. Nice images, for example, should be discussed in the context of a good question. Descriptive titles as opposed to popular titles should also be discussed for a good question. If the question is not good in the first place, all these debates become useless and just add confusion.

If a question should be closed, it should be closed, not have every detail of it debated on Meta.

The original is a bad question and should be closed, and this is a bad question because it has encouraged bad answers which, influenced by the original bad question, do not focus in the essentially trivial algorithm.

The OP of the original question did a terrible job in clarifying requirements. When you are trying to solve an algorithm you need to focus on the important ideas and not be distracted by data which may be related in the real world, but totally unrelated to the particular algorithm.

Croissants are such data. Not only their picture, but their very mention distracted everyone. It would be ok if the question had been otherwise clear, i.e. if besides the useless picture the requirements had been clearly isolated. But they were not.

In my opinion this question would only fit in a Stack Exchange site which does not exist yet: Requirements Definition (or perhaps Problem Definition). People (mainly non-programmers) would post their everyday problems there (Which bus stop should I choose if...? How many elevators do I need if...?) and the answers would clarify the exact requirements for them.

In our example, people would set to ask the OP if it's ok that someone brings the croissants twice in a row, or three times in a week, just by chance, as a result of the randomness. And two or three more questions specific to his problem. Then they would clarify the problem in a set of basic requirements, which would be the answer.

It would be a bad Q&A site, because it would be one in which people do your work for you and virtually noone else can benefit from it. In any case, it wouldn't be StackOverflow.

The original is a bad question and should be closed, and this is a bad question because it has encouraged answers which, influenced by the original bad question, fail to focus in its essential parts.

The original is a bad question

The OP of the original question did a terrible job in clarifying requirements. When you are trying to solve an algorithm you need to focus on the important ideas and not be distracted by data which may be related in the real world, but totally unrelated to the particular algorithm.

Croissants are such data. Not only their picture, but their very mention distracted everyone. It would be ok if the question had been otherwise clear, i.e. if besides the useless picture the requirements had been clearly isolated. But they were not.

In my opinion this question would only fit in a Stack Exchange site which does not exist yet: Requirements Definition (or perhaps Problem Definition). People (mainly non-programmers) would post their everyday problems there (Which bus stop should I choose if...? How many elevators do I need if...?) and the answers would clarify the exact requirements for them.

In our example, people would set to ask the OP if it's ok that someone brings the croissants twice in a row, or three times in a week, just by chance, as a result of the randomness. And two or three more questions specific to his problem. Then they would clarify the problem in a set of basic requirements, which would be the answer.

It would be a bad Q&A site, because it would be one in which people do your work for you and virtually noone else can benefit from it. In any case, it wouldn't be StackOverflow.

This is a bad question

The original should have been closed as off-topic because it doesn't show a minimal research effort and it doesn't demonstrate a minimal understanding of the problem being solved. It basically asks for a minimal understanding of that problem, as I said before.

This question dedicates a special attention to the original one, as if it was "special" in some way. As if it should generate a debate about lots of upvotes, nice images, popular title, popularity and close reasons altogether. It shouldn't. Each of these subjects should be (and has already) discussed independently on Meta. Nice images, for example, should be discussed in the context of a good question. Descriptive titles as opposed to popular titles should also be discussed for a good question. If the question is not good in the first place, all these debates become useless and just add confusion.

If a question should be closed, it should be closed, not have every detail of it debated on Meta.

Source Link
Daniel Daranas
  • 4.1k
  • 1
  • 22
  • 40

The original is a bad question and should be closed, and this is a bad question because it has encouraged bad answers which, influenced by the original bad question, do not focus in the essentially trivial algorithm.

The OP of the original question did a terrible job in clarifying requirements. When you are trying to solve an algorithm you need to focus on the important ideas and not be distracted by data which may be related in the real world, but totally unrelated to the particular algorithm.

Croissants are such data. Not only their picture, but their very mention distracted everyone. It would be ok if the question had been otherwise clear, i.e. if besides the useless picture the requirements had been clearly isolated. But they were not.

In my opinion this question would only fit in a Stack Exchange site which does not exist yet: Requirements Definition (or perhaps Problem Definition). People (mainly non-programmers) would post their everyday problems there (Which bus stop should I choose if...? How many elevators do I need if...?) and the answers would clarify the exact requirements for them.

In our example, people would set to ask the OP if it's ok that someone brings the croissants twice in a row, or three times in a week, just by chance, as a result of the randomness. And two or three more questions specific to his problem. Then they would clarify the problem in a set of basic requirements, which would be the answer.

It would be a bad Q&A site, because it would be one in which people do your work for you and virtually noone else can benefit from it. In any case, it wouldn't be StackOverflow.