Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

75%
+4 −0
Q&A How do I distinguish between self-doubt and objective recognition of fault?

It largely doesn't matter If you can tell which of two versions of a piece is better, you don't need to be able to tell if either is good. You'll edit to the better version, and repeat cycles of e...

posted 4y ago by Leo‭  ·  edited 4y ago by Leo‭

Answer
#2: Post edited by user avatar Leo‭ · 2020-01-16T19:53:39Z (over 4 years ago)
header level should be < question title
  • # It largely doesn't matter
  • If you can tell which of two versions of a piece is **better**, you don't need to be able to tell if either is **good**. You'll edit to the better version, and repeat cycles of editing and resting until the story is as good as you can make it.
  • Suppose angels then came from on high and told you whether the piece is excellent or terrible. What would you do with that information? It's already the best you can do!
  • # Your audience will tell you
  • In traditional publishing, publishers will not be shy about telling you if they like your writing.
  • For technical writing, you can run [hallway usability tests](https://www.techopedia.com/definition/30678/hallway-usability-testing).
  • If you don't have such a convenient audience, it can be hard to get feedback from beta readers; most are more cheerleader than critic. You might try one of the many online [critique](https://shutupandwrite.github.io/) [exchange](https://old.reddit.com/r/DestructiveReaders/) [groups](http://www.critters.org/), a writing workshop, or a professional editor.
  • ### It largely doesn't matter
  • If you can tell which of two versions of a piece is **better**, you don't need to be able to tell if either is **good**. You'll edit to the better version, and repeat cycles of editing and resting until the story is as good as you can make it.
  • Suppose angels then came from on high and told you whether the piece is excellent or terrible. What would you do with that information? It's already the best you can do!
  • ### Your audience will tell you
  • In traditional publishing, publishers will not be shy about telling you if they like your writing.
  • For technical writing, you can run [hallway usability tests](https://www.techopedia.com/definition/30678/hallway-usability-testing).
  • If you don't have such a convenient audience, it can be hard to get feedback from beta readers; most are more cheerleader than critic. You might try one of the many online [critique](https://shutupandwrite.github.io/) [exchange](https://old.reddit.com/r/DestructiveReaders/) [groups](http://www.critters.org/), a writing workshop, or a professional editor.
#1: Initial revision by user avatar Leo‭ · 2020-01-16T19:52:45Z (over 4 years ago)
# It largely doesn't matter

If you can tell which of two versions of a piece is **better**, you don't need to be able to tell if either is **good**. You'll edit to the better version, and repeat cycles of editing and resting until the story is as good as you can make it.

Suppose angels then came from on high and told you whether the piece is excellent or terrible. What would you do with that information? It's already the best you can do!

# Your audience will tell you

In traditional publishing, publishers will not be shy about telling you if they like your writing.

For technical writing, you can run [hallway usability tests](https://www.techopedia.com/definition/30678/hallway-usability-testing).

If you don't have such a convenient audience, it can be hard to get feedback from beta readers; most are more cheerleader than critic. You might try one of the many online [critique](https://shutupandwrite.github.io/) [exchange](https://old.reddit.com/r/DestructiveReaders/) [groups](http://www.critters.org/), a writing workshop, or a professional editor.