in reply to Consider this: What makes a good node title?
I can't imagine prejudicing the title against those who spell correctly is a good thing. I also have to believe that statistically, more people will spell a word correctly (or at least realize their mistake) than use any particular misspelling.
A title like "How do you reggex PERL" does tell you something about the poster, but certainly you would learn everything it tells you on reading the post itself. I don't see that as valuable information, and it's more likely to prejudice readers against the poster before they've even read the question.
Personally, I'd probably completely ignore a post with a title like "Program Line". Since most posts are responded to quite quickly, I think the more explicative title will cause it to draw more attention. I think it's also likely to make later searches easier rather than harder for most.
A title like "How do you reggex PERL" does tell you something about the poster, but certainly you would learn everything it tells you on reading the post itself. I don't see that as valuable information, and it's more likely to prejudice readers against the poster before they've even read the question.
Personally, I'd probably completely ignore a post with a title like "Program Line". Since most posts are responded to quite quickly, I think the more explicative title will cause it to draw more attention. I think it's also likely to make later searches easier rather than harder for most.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
| A reply falls below the community's threshold of quality. You may see it by logging in. |
In Section
Perl Monks Discussion