List your top 20 situations that might justify a police officer yanking a teenage girl out of her desk, slamming her to the floor and dragging her across her classroom.
I'm sure you could easily think of 20. Maybe she's pointing a weapon at the officer. Maybe she's physically threatening a classmate. Maybe the officer noticed she is trying to destroy evidence and has to be stopped. Maybe she's punching another student.
But I can GUARANTEE that "being disrespectful and disruptive" wouldn't be in your Top Twenty. In fact, I'll go further: prior to this week, if someone had suggested this as a potential situation, your response would have been "no, absolutely not, no fucking way does that action warrant that kind of treatment".
Let's up the hypothetical ante: the principal at your school is calling you at work to tell you that a police officer just yanked your teenage daughter out of her desk, slammed her to the floor and dragged her across her classroom, and she might have a broken arm. Because she was being disrespectful and disruptive, and wouldn't put her phone away.
Would your first thought be "Boy, that sounds perfectly reasonable and appropriate"?
Of course not.
But this week we have seen people falling over themselves to justify exactly those actions AFTER they happened.
In my opinion, it's because we have a cognitive bias towards justifying actions that have already happened, EVEN IF we would not be able to justify them before they happened. So we go from "there's no situation in which that would be the right thing to do" to "well, it happened, so there HAS to be a justification for why it did", purely because we need to create a narrative in which that makes sense. We don't like living in an irrational world where violence is unjustified: our brains are extremely uncomfortable with that reality, so our brains struggle to find the bits of the story that could allow that worldview to survive. Our brains love to tell stories that make sense, and are REALLY uncomfortable when they don't.
In this case, the brain immediately tries to put together a coherent narrative of cause and effect: Y happened, therefore the X actions that justify Y MUST have occurred immediately before, and our brains will go into overdrive to fit the facts into that narrative, no matter how much it has to distort the facts to do so.
What happened before? The student was disrespectful and uncooperative.
A ha! the brain says, slotting that fact into the "cause" box in the cause and effect flowchart. There is now something in the box, and your brain is taken out of its discomfort zone. The story now makes sense as a flowchart. Even though the fact you found doesn't fit neatly and seems to be rather much smaller than the box you put it in, there is at least something in the box.
That is, if you don't analyze it too much and ignore the poor fit. Because if you did, you'd realize it's not a good cause for the resulting observed effect, and then your brain would be thrown into discomfort again as its worldview is challenged. And our brains HATE that. Our brains like stories, and like cause and effect, and like coherence. The brain has its story, move on, nothing more to see.
This bias is so strong that if a person who has crafted this narrative is challenged on whether it makes sense and is justifiable, they go on the defensive quickly and strongly, because it feels like their entire worldview of cause and effect is being challenged. "I have a story!" says the brain, "and I have things in the boxes! Leave them be!"
And the way this works out in the conversation is that Person A questions whether Y is an appropriate outcome for action X. Person B perceives this as an attack on their worldview, and feels that criticism about placing the "disruptive, uncooperative teenager" fact in the "cause" box is a defense of the teen being disruptive and uncooperative. It's not, but the alternative is to take the fact back out of the box.
"Oh, so you think the teen wasn't being disruptive? Even the teachers and the other students agreed she was!"
"Oh, so you think that we shouldn't take any action against teenagers being disruptive and disrespectful?"
"Oh, so you think that the teenager was within her rights to do what she did before the officer showed up?"
Notice that none of those are really responses to the criticism that Y (being physically attacked and thrown to the floor) is not an appropriate response to X (being disrespectful and disruptive). They are responses to a perceived defense of X, as if the other side were defending the students actions as appropriate and above reproach or response. They are not, and no one has said they were. But it's easier to counter that perceived attack than respond to the real criticism, which means shaking up the boxes and putting the brain back in its discomfort zone.
And our brains hate that. Hate it so much that they will reroute attacks away from the uncomfortable facts and towards unrelated targets that are easier to defend.
I had a tough life, therefore there's no such thing as #whiteprivilege
Notice a pattern?)
For X = "a teenage student was being disruptive and disrespectful", and Y="a teenage student is body-slammed to the floor by a 250lb+ body-building police officer, possibly breaking her arm and then dragging her across the classroom floor", my position is that both of those things are TRUE. She was, by all accounts, being disruptive and disrespectful. He did slam her to the floor. Students being disruptive and disrespectful is something that should be addressed, appropriately. But for me to say that X does not justify Y is not a defense of X: it's a statement that Y is an appropriate response to a limited amount of actions, and X is most definitely NOT one of them.
But boy, do our brains not like the story we're left with if we have to face that reality. And that discomfort is at the root of our current conflicts on race, on gender, on privilege, on sexism, on religious freedom, on social and economic inequality. It's our cognitive bias towards stories that don't disrupt our worldview, that make sense (as long as we don't think about them too much), that don't challenge the many other biases we hold.
AND WE ALL DO IT. In fact, if you've reached this far down in this particular story, it's probably because (a) it helps you put things into the boxes in your brain that make you feel comfortable or (b) you are looking for the nitpicks to tear the argument apart so that you don't have to shake up your brainboxes. But if you are in (b), hopefully at least this helps frame the discussion away from the "you're defending X" position that no one is taking, and towards the "X does not justify Y" discussion we should be having.
Do the test first, then read on past the break....
After I completed the test (correctly), I read through the article and looked back at my thought process. I had 5 answers in a row where they were all correct. I was assuming the numbers must double. This is where my software engineer side kicked in: I wanted to break this. I wanted to make the test say "No, this does not satisfy the rule". Fiddled with it for another 20 answers before deciding I was initially wrong.
How'd you do?
This is a huge, unnecessary, and expensive loss of talent in a field facing a supposed talent shortage. Given that tech is currently one of the major drivers of the US economy, this impacts everyone. Any tech company struggling to hire and retain as many employees as they need should particularly care about addressing this problem.
- University of AlbertaMSc - Computing Science, 2010
- University of AlbertaBsc - Computing Science, 2008
- Surgeon Simulator
My name is Jeremy Nickurak. Some time ago I completed my M.Sc in Computing Science at the University of Alberta, where was working with Paul Lu's Trellis High-performance and meta computing research group. My chief areas of research interest are filesystem and resource access in a distributed/cluster context, especially where involving virtualization.
Since then, I've been working as a software developer on EMC's Vplex high-availability storage solution.
My resume is available, and I'll give proper consideration to anyone with a suggestion.
If you're interested in getting in touch with me, you can email me at firstname.lastname@example.org (slightly obfuscated to prevent spam bots from seeing it). You can also reach me at the same address on Jabber/XMPP/GoogleChat
- EMC CorporationSoftware Developer, 2010 - present
- University of AlbertaResearch Assistant, 2011
Defend your health care from Harper’s sneak attack
Harper just took his first chance to cut $36 billion from Canada’s public health care and he’s breaking the pact that all Canadians should g
Estimation is at the root of most software project failures | Rob Bowley
Synopsis. I believe estimation, and the way it's regularly misused, is at the root of the majority of software project failures. In this art
National Geographic Photography Contest Winners: 2011
More than 20,000 photographs, from over 130 countries were submitted to the National Geographic Photography contest, with both professional
Best Halloween Costume Ever: Use Two iPads to Create an Awesome Gaping H...
A very smart dude by the name of Mark Rober figured out that if you strap two iPad 2's to yourself, you can create this incredible, freaky h
Official Google Reader Blog: Powering Down Google Reader
We have just announced on the Official Google Blog that we will soon retire Google Reader (the actual date is July 1, 2013). We know Reader