Icyflare wrote...
Anyways, back on thread. Are you guys ever hesitant about what to comment on when leaving a review? I mean, I'm not a writing expert or even a lit teacher, so I can't feel justified when I go through a fellow writer's work and start tearing it apart like I want to sometimes. I can spot what doesn't work for me and what wouldn't work as a submission to a writing class, but at times, I don't know if I want to change something because I don't like the writing style or if it actually needs to be change. Usually, I just leave it if I don;t know how to suggest improvements. However, when I do comment on things in reviews, I am absolutely certain that these points I bring up could be worked on.
As a writer, any type of review works for me, whether it’s short or long, specific or vague, actual review or PM… I’ve probably stated it before, but I’m a firm believer in
all critique being useful. It’s up to me to draw conclusions.
If a review is looking to be really long (more than 10 items or so), I’ll probably reduce the review to the essentials, and note that I’m sending more specific comments by PM. For example, I regularly leave somewhat specific but short notes in reviews for DE3—there’s no fear of monopolizing reviews there!—but on the other hand, for Drussius’ first chapter, I left a short review and sent specific notes on the fairly minor issues by PM so as to not unnecessarily shadow the others.
As a reader, I’ve a couple rules that I more or less follow…if there’s something off, I’ll try to figure out what it is—but will mention it even if I can’t quite put my finger on it. Even a vague hint may help the writer identify a problem spot (maybe they already were unsure of a passage, or maybe another reviewer is able to refine the comment, or…) Pacing issues are particularly hard to describe, and it would usually take longer than I want to take to fully explore the issue, so I try to note those fairly coarsely and let the author figure out if and which parts to adjust.
I don’t usually specifically look for grammar issues, but sometimes those, typos, word misuse stick out, and I’ll note it.
One bad habit I have is tech stuff…I’m a bit harsh on those, at least judging by the (lack of) reaction to the same things by the other reviewers.
I’m also not terribly good with positive feedback…I should probably try to work more of that in, comment on specific lines characters use, specific background information and so on, for example. Usually I just end up saying that the characterization is good, if it is, without going much deeper into it—but the author would probably benefit knowing which things work in particular.
…
I also tend to write way, way too much…
…
On a totally but not quite unrelated note, I finally just added a dotjs script to hide all forum topics that contain the word ‘synthesis’, because I keep wasting time getting tangled up in trying to talk some sense into people.
Modifié par lillitheris, 17 juillet 2012 - 08:32 .