Critiquing vs Criticizing

AChubbyBlackCat · 2019-01-28T21:05:15.154Z

I mean… we could argue that 'till we’re all blue in the face of what a good and fair critique should look like based on the dictionary definition, but there’s a ton of outside factors to step back and consider in terms of any type of feedback.

Maybe not enough time to time out something that’s paragraphs long. Maybe they feel that their insight isn’t valuable or worthwhile or just a rehash of what someone else has said. The list goes on and on and on.

Ultimately, feedback is subjective since it’s based upon opinion and opinions aren’t something that can be proven to be right or wrong.

And just to double down on my previous point, you could think of giving feedback in two very extreme examples as either being a drill sergeant in an army and screaming in someone’s face or just glossing over what could be improved, reinforcing that nothing needs improvement and that everyone who thinks so is just mean.

Ideally, feedback shouldn’t on either end of these two extremes for obvious reasons.

If your feedback mimics a drill sergeant, the author will ignore you, think that you’re the problem, and will probably never listen to you from that point forward. If your feedback is just sweeping everything that could be improved under the rug, you’re basically helping them put out a “faulty” product and you’re not helping them improve to be a better writer.

It’s been brought up a couple of times, but I’d like to chime in and say a 5 Star rating system is not a very good system to begin with for various reasons. The most relevant to an author is that it encourages buyers to do the bare minimum (just leave a star or several) without going into detail as to why they gave the product that rating.

The 5 Star system is most appropriate for products that are tangible i.e. DVDs, a phone, etc. since it’s probably easier to understand why you gave something a 1 Star if the product had a giant crack down the middle of it.

And let’s not get started on customer by customer “standards” of how something should qualify as a 1 Star or 5 Star.

Meira_Litch · 2019-01-28T21:11:51.196Z

The thing is, no one is saying beta testers shouldn’t be sincere, what people is saying is, a beta tester shouldn’t do more harm than good. And if you go full blunt with negative points about the game, that is more likely going to ruin the author, rather than helping them, since the chances of it coming off as plain hate are higher.

Is not the same to have someone tell you a loved one has died in a delicate, compassionate way, than just tell you “your sister died, bye”.

poison_mara · 2019-01-28T21:17:42.446Z

And As i can’t stop adding I am saying be sincere POSITIVE negative and posible options.

Sincerity doesnt mean be an ass. Or spit fire breath

For instance sincerity is

I found this scene lack in a evil choice I will like have a option to be more grumpy there because my character don’t like that character trying to flirt with her.

I like X it is very well designed and has a good development . I found also Leon incredible cute…

So well thats part of my this weekend feedback to Keepers … I have not eaten alive Also Similar example you could see in Six game .

Meira_Litch · 2019-01-28T21:21:50.665Z

Then I think is all a misunderstanding

No one is saying to not be sincere, being delicate or sugar coating, as others describe it, doesn’t mean you are lying at all, it just means you are being tactful. Being sincere and tactful are not opposites after all

poison_mara · 2019-01-28T21:25:17.850Z

Of course I am being more tactful later. Tactful is sincere too. What i was trying to say with Sincere is not rude It is say the truth clearly not trying to hide it with white noise.

Being tactful and CLEAR because if you aren’t clear author can’t understand really what are you saying.

TSSL · 2019-01-29T00:24:25.489Z

will:

sandwich critique

I know it’s a popular method of giving critique, but it’s so pervasive that it can often come across as disingenuous.

I wouldn’t say that it’s really necessary to rigidly adhere to the sandwich structure, but I think that including some positives alongside the negatives is important, and beginning with the positives is going to be a lot more encouraging than the reverse. (The close, on the other hand, I think just some polite “good luck with the rest of your writing” or suchlike can be enough.)

As for why positive feedback is important, well, I’ll quote myself so I don’t need to type it all out again…

Positive feedback is more useful than a lot of people realize. For one thing, it demonstrates to the author that this feedback is coming from someone who appreciates something about the story/game, so any suggestions that tester has are coming from someone who at least somewhat gets the project and could be part of its audience. It also shows the author what’s working, what to do more of, what strengths the author can play up. And, well, motivation is important too.

Really, if an author receives some feedback that is nothing but negatives, the author is liable to conclude “well, this reader isn’t part of my audience anyway, so I’ll may more attention to suggestions from people who are interested.”

As far as structuring feedback, I also usually move from the big level feedback toward the small level stuff. Typos and bug fixes can generally just be plopped at the end, under a [details][/details] tag, as you don’t really need them to take up a big bunch of space in the thread.

Camille622:

I also think it’s important to just give your personal impression,

Oh yeah, and even giving more neutral impressions can still be useful. Just things like what you think characters are like, or what you think is going on in the story, etc. Sometimes what the author intends to convey isn’t matching what the reader is getting out of it, and you’ll never know it unless you check.

easternsybil · 2019-01-29T01:11:36.778Z

I know that everyone will have differing opinions regarding the positive to negative feedback ratio, but there have been lots of studies done on how people learn and develop ideas depending on feedback received.

I got to sit in on a live VR-based study several years ago, where subjects were asked to solve a particular problem. When they were wrong, a big red ‘x’ appeared and a buzz sounded. When they were right, a green checkmark appeared and a little dingy sounded. The experiments were still in the early stages, but the info they had gathered was that the subjects were (predictably) more receptive to the positive reinforcement.

Studies I searched up had different results, largely focusing on the importance of a mix of positive and negative feedback. Hard to improve if you dont know what you’ve done wrong, but also humans are silly and like the green checkmarks. If the point of critiquing and providing feedback to WIPs is to help the author learn to produce a better product, I think it’s worth it to take into consideration how people work.

Memory & Cognition

Comparing the effects of positive and negative feedback in...

Categorical learning is dependent on feedback. Here, we compare how positive and negative feedback affect information-integration (II) category learning. Ashby and O’Brien (2007) demonstrated that both positive and negative feedback are required to...

Attention, Perception, & Psychophysics

The effects of positive versus negative feedback on information-integration...

A number of studies have shown that in category learning, providing feedback about errors allows faster learning than providing feedback about correct responses. However, these previous studies used explicit, rulebased tasks in which the category...

Jacic · 2019-01-29T04:16:52.322Z

easternsybil:

When they were right, a green checkmark appeared and a little dingy sounded. The experiments were still in the early stages, but the info they had gathered was that the subjects were (predictably) more receptive to the positive reinforcement.

Haven’t read the links, but shouldn’t be a surprise. It’s been known for a long, long time and that’s why slot machines are designed the way they are with all their jingling sounds and flashing lights. You don’t get buzzers for non-successful runs, only re-enforcement for the successful ones. (That’s not the only thing they use, but it’s definitely a factor.) But yeah, there is still a balance to be made between encouragement and the information needed (which is often crit) so you can efficiently improve.

niisan · 2019-01-29T14:17:47.144Z

A lot has already been said on the topic and reading everyone’s opinions definitely made me think how to improve my own feedback-giving-skills AND how to ask the right questions to get the answers I need to improve my story.

As an author, I appreciate all types of comments, from “I liked it” to “Can we do x?” or “Why did you do that?”.

I would definitely like to hear what didn’t work for people, because I can’t fix it otherwise. I’m new to writing for public consumption, so any kind of feedback is valuable. As long as the reader doesn’t say “Your story sucks” (not that I have seen it happen on this forums) and stops at that. At least tell me why do you think it’s bad. The more specific you get, the better.

As a reader I struggle with listing the negatives because a) maybe what bothers me is simply a result of difference in tastes, b) my lack of experience in both writing and giving high leveled feedback. Knowing which things I should pay attention to (eg. pacing, story inconstancy, grammar) definitely helps.

MeltingPenguins · 2019-01-29T17:53:00.432Z

On a related note:

How many people check a game’s code (as spoilery as it is) when/before giving feedback?

Eiwynn · 2019-01-29T17:56:58.365Z

MeltingPenguins:

How many people check a game’s code (as spoilery as it is) when/before giving feedback?

I still have major problems accomplishing this on published games. I’ve only successfully looked at code a few times, even with over a hundred attempts so far.

For WiP, I don’t do this unless the author requests it; I try to keep my feedback linked to a “in the wild” read instead of a “behind the curtain” read.

MIGSey · 2019-01-29T18:03:42.071Z

What about Zombie Exodus: Safe Haven ? I can understand for other games, but seeing how you are (partly) involved in its development… just curious is all.

Eiwynn · 2019-01-29T18:07:29.418Z

MIGSey:

What about Zombie Exodus: Safe Haven ? I can understand for other games, but seeing how you are (partly) involved in its development… just curious is all.

That is different. With Part 2 material, I had to understand the code better to write. Even so, Jim is in complete control of the code because he is a wiz at it and I was best at writing.

Going forward I will be moving back into the shadows, testing as before.

MeltingPenguins · 2019-01-29T18:17:39.544Z

Eiwynn:

MeltingPenguins:

How many people check a game’s code (as spoilery as it is) when/before giving feedback?

I still have major problems accomplishing this on published games. I’ve only successfully looked at code a few times, even with over a hundred attempts so far.

to me it’s become a bit of a habit (and I hope it is okay with the staff and authors) to dive into the code when i find something odd. Just to see ‘okay, we have all screamed at code after we missed something, let’s see what it is, maybe i can suggest some fix’

And I know that people checking my code helped me with a lot of things

poison_mara · 2019-01-29T18:22:41.198Z

I personally only look code if authors asks for. Most of my feedback comes from perspective of someone blind and or a role player being blind and ss see my reaction to plot twist are far useful from a blind perspective. Is also good when I make what i called testing coherence.

I choose conflicting choices and not what is looking more logical to see if game has coherence o balance choices. For instance if @Cataphrak guns I found A loop of death in one scene if you hadn’t the best stats you could ended in a eternal returning to chapter after dying in battle.

Another important check of coherence is If opposites stats shifting that could cause in game like empyrean in same scene be a great lockpicker to have never seen a lock and have no idea how use the tools. Those are details that need a game running and aren’t visible code wise.

Eiwynn · 2019-01-29T18:24:06.075Z

MeltingPenguins:

And I know that people checking my code helped me with a lot of things

Informed feedback is very helpful. Many, if not most people who are active testers here do it.

Which is why I often do not.

The author usually needs both categories of feedback - and often both types are helpful in different ways.

AChubbyBlackCat · 2019-01-29T18:26:55.983Z

Usually after I’ve given feedback or after I’ve read the demo all the way through if I’m confused about which choices/options raised or lowered some stats that I wasn’t expecting. Otherwise, I check the code to pass a pass or fail option if I haven’t passed for the fifth time in a row.

ParrotWatcher · 2019-01-29T18:32:36.855Z

MeltingPenguins:

to me it’s become a bit of a habit (and I hope it is okay with the staff and authors) to dive into the code when i find something odd. Just to see ‘okay, we have all screamed at code after we missed something, let’s see what it is, maybe i can suggest some fix’

I certainly feel that “Something’s wrong here” is far less useful than “I spotted a problem in this exact spot; here’s what’s wrong (and possibly how to fix it)”.

Dark_Stalker · 2019-01-29T18:32:46.834Z

MeltingPenguins:

How many people check a game’s code (as spoilery as it is) when/before giving feedback?

I’ve checked it once for feedback, and that was mostly to help the author with a bug. All the other times were me looking to check which stats to raise. Though I do complain about stat increases sometimes.

spunkycatninja · 2019-01-29T18:55:41.777Z

poison_mara:

I personally only look code if authors asks for. Most of my feedback comes from perspective of someone blind and or a role player being blind and ss see my reaction to plot twist are far useful from a blind perspective. Is also good when I make what i called testing coherence.

I think that way as well. Unless I’m editing, I don’t go poking around in the code unless asked. I feel the testing should be done as a player. If there are concerns, then bring it up to the author. There are lots of things to be missed by looking at just the code.