-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Great writing should come back nearly clean #25
Comments
I mention this because the defaults of tools like write-good are extremely noisy, false alarming on many words and phrases (e.g., banning the word "only", which is sometimes used improperly, but is often part of a sentence's essential logical structure). |
The idea is really just that you shouldn't introduce a new rule that alone finds tens or hundreds of errors in top-notch writing. That would be surprising and would suggest that your rule was too noisy. We'll have to figure out the right metric to use here --- how we tell if a rule is too noisy. Maybe we can create a metric like words per error (wpe) and set a threshold for top-notch text and normal text. |
why did you close this I think its a good point? On Tuesday, January 27, 2015, Jordan Suchow notifications@github.com
|
It's fixed! The test suite runs the linter on all the samples in |
It would be good to include an automated test sweet that runs the linter over writing that is written by a great author and has already been heavily edited and copyedited (e.g., an essay from The New Yorker that went on to win the Pulitzer prize in nonfiction) . The linter should be nearly silent.
The text was updated successfully, but these errors were encountered: