The Stack Overflow podcast is back! Listen to an interview with our new CEO.
5 replaced http://pm.stackexchange.com/ with https://pm.stackexchange.com/
source | link

The FAQFAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questionsquestions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this question before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1Q1

The FAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this question before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1

The FAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this question before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1

4 replaced http://meta.pm.stackexchange.com/ with https://pm.meta.stackexchange.com/
source | link

The FAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this questionquestion before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1

The FAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this question before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1

The FAQ discourages tool recommendations - it specifically says that this site is not for tool recommendations. Tool recommendations tend to be localized (localized in time - because one version of a tool may be very different from another. Localized in applicability because if the requirements aren't well expressed, then the "best" tool for you may be merely average for most people.) Tool recommendations are difficult to generalize for everyone - every requirements set is very specific.

The counter argument is questions that are reasonably specific and well formulated. please feel free to insert other examples; I know there are many We get a lot of questions about tool recommendations. I've been perhaps overly enthusiastic about discouraging tool recommendations.

Area 51 says we need to raise the number of questions asked here/day in order to graduate from beta. I admit that I'm concerned about the discouraging effect every time I vote or comment to close a question. I believe that that part of the value of a site is consistent culture, and one of the fair ways to ensure that is to make the FAQ correspond to the behavior. But I'm concerned that we're (I'm) discouraging potentially enthusiastic participants.

It appears this isn't the first time we've contemplated this question before.

Rather than continue my quixotic crusade to follow the FAQ, I thought I'd ask the meta question - which do we want? The PM:SE described by the FAQ, or the PM:SE that we're getting? How much effort should we devote to preserving the PM:SE we want? Is there a way of bounding tool recommendations that conforms to the SE: model of voting for the best answer to a generalized question?

Someone asked for references: Q1

3 edited tags
| link
2 added 90 characters in body
source | link
1
source | link