We continue to make that abundantly clear.
Military interventions in Syria are a complicated issue on which reasonable minds can disagree. But one cannot justify military strikes on Syria on the basis of the ghastly human rights atrocities being perpetrated there and then only admit less than a dozen Syrian refugees into the United States (thus far this year).
Our policies with respect to immigration and refugee rights continue to be complete and utter disgraces.
Saturday, April 14, 2018
Tuesday, April 10, 2018
David's Personal Top Ten Video Games
This is something I've been wanting to do for a long time. It is a personal list, reflecting the games that have stuck with me the most over the years. I'm not enough of a gamer to claim it is anything comprehensive, and it has a strong bias to the sorts of genres that I like. Nonetheless, I'd stack these games against any that have been made in my lifetime.
Anyway, without further adieu ....
Anyway, without further adieu ....
Honorable Mentions:
Portal 2: How can
a game with virtually no “dialogue” (if that means conversations between two
characters) have some of the best spoken lines in all video game history? I
have both the original and a capella versions of the Turret Opera on my iTunes
(yes, I have “Still Alive” as well).
Railroad Tycoon II:
A brilliant simulator that makes you actually feel like a turn-of-the-century
robber baron (by far, the game is most fun to play when set in the late 19th
century). If every man goes through his “trains!” phase, this was mine. As in
real life, I am not good at playing the stock market.
Horizon: Zero Dawn:
Robot dinosaurs! Incredibly, Horizon:
Zero Dawn takes a core concept that sounds like word association from an
over-caffeinated twelve-year boy and makes an entirely serious game about
it—and it works. It works so well, in
fact, that I loved it despite the fact that the plot and entire world-building
background centers around my single greatest phobia (no, not that—being alive
for the extinction of humanity).
10. Sid Meier’s
Gettysburg: I find it odd that very few games have sought to replicate
Gettysburg’s spin on an RTS—focusing combat around regiments rather than
individual units and prioritizing morale over raw numbers. But the thing I like
best about Gettysburg—and sadly it’s mostly unique too—is in how it
concentrates on controlling territory
(and terrain). Many RTS games, for me, might as well have a blank screen over
80% of the map between my base and my opponent’s base. You build up your force,
and then try to swarm your opponent before he or she swarms you. But in
Gettysburg, the goal of missions is not “wipe out your opposition”. It’s to
capture and hold a ridge, or dig in and hold an exposed farmhouse.
My only critiques are that I want this game to be bigger. I
want it to encompass dozens of maps spanning the entirety of the Civil War. I
want to be able memorize even more obscure Union and Confederate generals and
wonder if they really were “mediocre” or if that was just a game balance
decision. The random battle generator is okay, but this game screams for
user-created expansions which I’ve never been able to find.
9. Crimson Skies:
A pulpy fun flight simulator taking place in an alternate history 1930s where
America has fractured and Zeppelin travel rules the day. The game doesn’t
hesitate to lean into its concept (phrases like “broad” and “floozy”
abound), and it does a great job world-building in a relatively short period of
time. Somehow, I could meet an enemy “ace” for the first time in the middle of
a mission and yet still feel like we had a history of epic dogfights together
of which this was only the latest. Meanwhile, each of the locations the game
takes you to (Hawaii, the Pacific Northwest, Hollywood, the Rocky Mountains,
and New York City) are a blast and a half.
A sequel, High Road to
Revenge, was released on Xbox and leaned a little too hard into the
arcade-y elements (power-ups, automatic evasive maneuvers with the press of a
button, and so on). But the original PC game was just right—planes flew exactly
like how someone who knows nothing about planes thinks planes fly, which is
just perfect. You felt like an ace pilot because of your skill (even though
behind the hood the game is really holding your hand). Piloting a gyrocopter through half-built New York City skyscrapers, or a prototype single-engine through the Hollywood "O", is great. Doing it to evade local security, then doing a loop and turning both guns on them -- well, that's the cat's meow.
8. Mass Effect (Trilogy and Andromeda): As far as
I’m concerned, the definitive space opera (even muscling out Halo). Fabulous voice acting (listening
to Martin Sheen play evil Jed Bartlett is one of the great joys of my life) and
memorable plot lines pair with a morality system that at least inches away from
“basically decent person or utter asshole.” The universe feels genuinely alive,
like there’s an ecosystem and civilization that you’re very much a part of, but
also moves in your absence.
I can’t really separate out the core trilogy games from one
another (each sequel seemed to simultaneously step slightly forward and back),
which is not I think an uncommon position. What may be more uncommon is that I
think Andromeda stands right in there
with the core series. Yes, it was disappointing that it took us to a brand new
galaxy and only gave us two new species (while eliminating many of the more
backgrounded Milky Way aliens). But I was much more disappointed that there
will be no DLC or sequels to continue the story and tie up loose ends.
7. N and N++:
There can’t be any serious controversy that N
is the greatest Flash game ever made. While Flash demands simplicity, N is not so much simple as it is elegant. It is the perfect balance of
speed and control, thoughtfulness and twitch-trigger reflexes, serene
relaxation and butt-clenching tension. Once you master the floaty physics and
the unique enemy styles, you will truly feel
like a ninja—stripped to its core essence and deprived of all the usual but
unnecessary bells and whistles. A virtually unlimited supply of levels
guarantees you endless gameplay.
And so it is unsurprising that N was one of the rare flash games that made a successful jump to a
full true game (in the form of N++),
one that has a strong claim on being the greatest platformer ever made. The developers were wise not to disturb the
basic formula: run, jump, and slide around a level, dodge obstacles and traps
that will kill you instantly, reach the exit. Repeat ad infinitum. But N++ adds just a splash of additional
flavors and spices into the mix. A perfect trip-trance soundtrack that sets the
mood perfectly (and may single-handedly stave off keyboard-smashing
frustration). A few new enemy types that deepen the game without ruining its
austere grace. And perhaps most importantly, it adds a bunch of extra,
semi-secret challenges (which can be used to unlock still more levels) waiting
for the very best-of-best players.
Of all the games on this list, I might be in absolute terms
“best” at N++ (there are a
non-trivial number of levels in the game where I have a top 100 or even top 10
score on the global leaderboards). And yet there is not the slightest chance
that I will ever perfect this game, or even come close to it. Nor is there any
chance I will become permanently sick of it. A simple concept, executed
brilliantly. The perfect N++ level is
also the perfect description of the game.
6. Final Fantasy IX:
The question was never whether a Final
Fantasy game would make this list, only which one. I’ve long had a
soft-spot for FFIX, which I feel is often overlooked inside the series (in part
because even on release it seemed players were already looking ahead to the
Playstation 2). Yet it’s hard to find fault in Final Fantasy IX as an emblem of a straight-forward JRPG. It has a
moving story, fun gameplay, beautiful music, loads of quests to do and places
to explore, a fabulous supporting cast (Vivi might be my favorite Final Fantasy
character ever written), and a lead character you don’t want to punch (*cough* Final Fantasy X).
Final Fantasy IX is
often described as “nostalgic”, and despite the fact that it was only the
second game in the series I had ever played, I got that feeling instantly. Try
listening to the soundtrack
for “Frontier Village Dali” without feeling a little melancholic. You don’t
even have to have played. But I recommend that you do.
For the record, my ranking of Final Fantasy games that I’ve
played goes: IX, VII, XII, XV, X, XIII.
5. Assassin’s Creed:
Brotherhood: One difficulty in judging
games within a series is how to compare an earlier game which still had
some rough edges but represented a quantum leap forward versus a later game
which didn’t do anything super-novel but tweaked the formula to perfection.
That, in a nutshell, is the difference between Assassin’s Creed II and Assassin’s
Creed: Brotherhood. Now, for me, this is an easy call for idiosyncratic
reasons—I played AC:B before AC II, and so I experienced the former
as both the perfected model and the
quantum leap forward as compared to the original game. But I respect that for
those who played the series in order, this is a harder call.
What should be easy for anyone is to agree that together, Assassin’s Creed II and Assassin’s Creed: Brotherhood represented
the AC series reaching its full potential. Ezio continues to be the best
protagonist the series has seen to date. Renaissance Italy likewise is the
ideal setting for both AC’s vertical and horizontal platforming elements and
its shadowy-conspiracy/secret-history plotline. As a franchise, Assassin’s Creed really launched the
parkour/open-world exploration genre, and Brotherhood
was the first game where every single element of what that genre could be
came together. Other more recent games have been tons of fun (Black Flag and Syndicate are I think highlights), but these two games are the
reason this series is so iconic.
4. Might and Magic VI:
The same problem posed by AC2 versus Brotherhood emerges with Might and Magic VI and VII—except here, I did play them in
order. Like the previous entry, I do think that VII ultimately improves upon the formula set out in Might and Magic VI. It’s more versatile,
has more replay value, a touch more balanced (and that’s not getting into
ArcoMage) … all in all, probably a better technical game.
But Might and Magic VI
is for me iconic—it may well be the first RPG I’ve ever truly loved (and given
the way this list is stacked in that direction, that’s saying a lot). Virtually
all the things that characterize what I love in games today, it had in at least
skeletal form. Open world exploration? Check: It was the first game where I
felt like I was a true pathfinder—meticulously crawling over every corner of the
map to find each obscure bandit’s cave and goblin fortress. To this day I still
have the lay of the land in Enroth basically memorized. Overly detailed
worldbuilding text to read? Absolutely: my obsessive-streak came out in reading
every single artifact description, conversational option, and quest
backgrounder (it is canon that Enroth, and the entire planet it resides upon,
was blown up in a magical explosion—a fact I’m still resentful towards 3DO for
long after it disappeared into bankruptcy). Slight genre-bending? The splash of
Sci-Fi onto the fantasy setting was delightful to discover for someone who had
never played any of the prior entries in the series. And some of the
music—well, the White
Cap theme is a thing of beauty, and on my computer “Adagio in G Minor for
Strings and Organ” is still listed as “Church Dungeon Music.”
3. Heroes of Might and
Magic III: If comparing earlier, more revolutionary games against newer
more polished ones presents a problem in the Assassin’s Creed and Might
and Magic series, it presents no trouble at all in Heroes of Might & Magic. That’s because the third installation
in the series both represented a huge jump forward from what came before and is unquestionably the best entry in
the overall sequence.
Sure, some of the expansions are a bit goofy, but they still
work—sharpshooters and enchanters are massively overpowered, but they’re
generally used in missions that would otherwise be impossible. But the main
campaign is fabulous—a surprisingly intricate and interwoven plot that bridges Might and Magic VI and VII compliments outstanding strategy
gameplay. And that doesn’t even get into the acre of standalone maps provided,
plus countless more available on the web thanks to a map editor so intuitive,
even I can use it (I’m terrible with map editors).
As a result of all of this, Heroes III is maybe the only game on this list that can compete
with N++ regarding infinite
replayability. This is fortunate, because—given the fact that Heroes III was a full-budget release and
was not supposed to be “simple”—it ages incredibly well. Even the graphics hold
up (no need for that remastered remake—which doesn’t even include the
expansions!).
2. Witcher III:
As you may have noticed, this list has a strong bias towards RPGs. My
preference is toward “Western” RPGs (which have a go-anywhere/do-anything
exploration mentality) compared to “Japanese” RPGs (which are more linear and
story-driven), but Witcher III does
an incredible job of synthesizing the best of both. It has a huge open world to
explore, one that feels alive and dynamic—but there is also an incredibly rich
story filled with deep, well-written characters (of which Geralt—the player
character—is but one).
Gameplay-wise, Witcher
III really hits the perfect balance. I simultaneously felt like the biggest
bad-ass in the room, but also like a single slip in concentration or bit of
overconfidence and my corpse would unceremoniously end up at the bottom of
whatever cave I was in. But Witcher III
particularly stands out in how it subverts certain common RPG tropes. You are a
hero, but you’re not particularly well-liked. You’re a powerful warrior, but
you’re still ultimately treated as a pawn in larger political machinations.
Your interventions do not always save the day, and sometimes don’t even make
things better. If a mission starts with a villager worrying that their beloved
has gone missing, nine times out of ten that person has been devoured by a
monster well before you ever get there. While many games claim to place the
hero in difficult moral dilemmas, Witcher
III is a rare case of following through (some games might give you the choice to let a trio of witches eat a group of
kids whom you recently played hide-and-seek with, but few make it so that might
actually be the more moral of the
options in front of you). There’s even a quest where you help a knight rescue a
lady in distress from a curse, then lecture him that he’s not entitled to her
romantic attention as a reward (talk about a timely intervention in the video
game genre!). Over and over again, the game reinforces the message that being
really powerful and doing “the right thing” isn’t enough to fix a fundamentally
broken system.
Most impressive is the emotional impact that Witcher III dishes out. Sometimes this
is a result of rich character development that pays off over the course of the
entire game (as in “The
Last Wish” quest). But sometimes it shows up in even relatively minor
sidequests—the epilogue of the
“Black Pearl” quest was one of the more brutal emotional gut-punches I’ve
experienced in a video game. Ultimately, this was a game where one always felt
like each character was a person—they were imperfect, they had their own
interests, hopes, dreams, strengths and foibles, and while you were a little
better with a sword and gifted with some preternatural abilities, you were
still only one player in a much bigger narrative. As a result, Witcher III might well be, in my
estimation, the perfect RPG.
Oh, and Gwent is ludicrously addictive. Let’s not forget
that.
1. TIE Fighter: I don’t think this list has a particularly “modern”
bias. Still, there’s something impressive about the number one game on this
list also being the oldest by some measure. TIE Fighter originally came out in
1994, and the definitive Collector’s Edition was released in 1995. It is, to
this day, one of the best games ever made. And that’s not a retrospective
assessment. Star Wars: Tie Fighter holds up even played right now.
For starters, it is one of the few
elements of the Star Wars universe to get the Empire right. I’m not saying that
the Empire is the real protagonist of the series. I am saying that they wouldn’t
view themselves as evil—as much as
naming spacecraft “Executor” and “Death Star” might suggest otherwise. TIE
Fighter is quite self-assured in presenting you as being a force for law and
order in the galaxy, battling not just seditious rebels but pirates, smugglers,
and other anarchic forces that threaten to tear civilized life apart.
Let’s start with something often
overlooked in TIE Fighter: the music. It’s probably the only context that the
phrase “kick-ass MIDI soundtrack” makes sense. But that’s not even the half of
it. The iMuse system dynamically and seamlessly arranges the musical cues to
reflect what’s going on around you in the mission—you can literally follow
important mission updates (e.g., a wingman being shot down, or reinforcements
arriving) simply by the way the melody shifts. I’m not sure I’ve ever encountered
anything quite like it since. To this day, the number that accompanies an
incoming enemy capital ship fills me with exhilarated dread.
Gameplay-wise, TIE Fighter is
almost shockingly rich. The core mission requirements are challenging, but by
no means out of reach. But embedded in each level are a series of secondary and
secret bonus objectives. These unlock a parallel plot of the Emperor’s Secret
Order—but always present a brutal risk/reward calculus. That’s not unrelated to
the fact that you’re often flying, well, TIE fighters (not noted for their
durability)—but the challenge extends well beyond physical peril. TIE Fighter actually
gives you an “invincibility” option if you want it, and yet even with it on
some of the later missions and bonus objectives will strain every piloting
skill you’ve ever developed.
Most importantly, the secret
objectives usually are more involved than “blow up everything in sight.” They reward
initiative and exploration. Maybe your primary mission objective is to destroy
a rebel space station. But just before it goes down, you spot an escape shuttle
fleeing the station. Take it out? Maybe—but maybe the occupants are VIPs best
taken alive. So you switch to ion cannons and disable it for capture. Yet that
extra time you just spent has given the rebels enough breathing room to summon
reinforcements—now an enemy cruiser is bearing down on you. Take out its
missile launchers and clear path for bombers while praying that your own Star
Destroyer will arrive soon to back you up. All on the fly. All while
dogfighting starfighters, dodging mines, giving your wingmen orders … it’s
insanely, beautifully chaotic.
Did I mention this is all
happening in 1995? 90% of games
released today don’t have that kind of depth or spontaneity. In terms of
playability, replayability, and just plain fun, TIE Fighter stands alone, and
unchallenged.
Monday, April 09, 2018
Preemptive Strikes in Antidiscrimination Law (Or: Why You Need a Union!)
Last week, the Eighth Circuit Court of Appeals decided the case of Hales v. Casey's Marketing.
Lauren Hales was an eighteen year old employee working the graveyard shift at Casey's General Store. At 1:45 AM, a customer came in and starting making sexually suggestive comments towards her. In an attempt to avoid the man, Hales stepped outside to take a cigarette break. The man followed her, blocked the entrance to the store, and continued making sexual remarks.
Hales, who had previously been sexual assaulted, told the guy to "back off". The customer replied "what are you going to do about it?", at which point Hales extended her cigarette to ward him off. Instead, the customer stepped towards Hales, burning his arm on her cigarette in the process.
The next day, the customer complained to a Casey's manager that Hales had burned his arm. The next time Hales reported to work, a manager asked her if "anything out of the ordinary" happened on her previous shift. She forthrightly reported the cigarette incident, but said she had done it in self-defense.
Hales was then terminated.
She sued, alleging sexual harassment and retaliation -- and the Eighth Circuit just rejected both of those claims. The harassment claim failed because the customer's conduct wasn't "severe or pervasive" enough to constitute sexual harassment as a matter of law (the Eighth Circuit apparently hasn't decided whether a company can be held liable for harassment done by a customer, but it assumed for sake of argument that it could). The retaliation claim was rejected because it was filed too late, but apparently the district court had also indicated it should fail because Hales was not engaged in protected activity under Title VII.
Here's the thing: I'm not sure this decision is wrong as a matter of (current) law. The "severe and pervasive" threshold necessary to make out a harassment claim is extremely (I'd say ludicrously) high, and I know of no case law which addresses self-defense steps as a form of "opposing" harassment in the workplace.*
But even if the case "rightfully" lost, all that demonstrates is that antidiscrimination law -- even when "correctly" applied -- isn't sufficient to protect vulnerable workers (even from discrimination).
In fact, the structure of antidiscrimination law in many ways encourages employers like Casey's to act in precisely this fashion -- terminating employees who are the victims of sexual harassment (whether by customers or coworkers) as a "preemptive strike" before they're able to put together a legally cognizable claim of discrimination. Even if one doesn't think that antidiscrimination law should expand to create liability for a single case of customer harassment, there's surely something perverse about it allowing (or even encouraging!) a young woman to be fired because she refused to tolerate a customer harassing her.
When I read this case, it reminded me of one of the very first employment discrimination cases I read which got me hot under the collar -- Jordan v. Alternative Resources Corp. In that case, Jordan -- in accordance with company policy -- reported a coworker who, while watching news coverage that two Black criminals had been arrested, exclaimed "[t]hey should put those two black monkeys in a cage with a bunch of black apes and let the apes fuck them." His supervisor took decisive action ... against Jordan: changing his work hours to less desirable times, making derogatory comments towards Jordan, and then -- within a month of the initial complaint -- firing Jordan. Jordan sued, claiming his termination was retaliation for filing his complaint.
Title VII only protects against retaliation if you're opposing an act covered under Title VII. In Jordan, the Fourth Circuit concluded that the single racist remark Jordan reported could not alone have sufficed to create legally actionable harassment (again, not being "severe or pervasive" enough to qualify), which means he was not "opposing" covered conduct, which means that his company was not retaliating against him as a matter of law (even though, again, company policy required that Jordan file his complaint).
Jordan argued that his complaint should have been protected because it covered action that, if left unabated, would have eventually ripened into unlawful harassment. The court refused to make the extension, and the result is an obvious Catch-22: Jordan has to report conduct that is not "yet" harassment in order to obey company policy (and preserve a potential future harassment claim), but he can be retaliated against for filing the reports.
But there's a deeper problem in the incentive structure this rule creates: As soon as an employer begins to observe incipient harassing conduct that has not (yet) risen to be legally actionable, it probably should terminate the victim before a sufficient record of wrongful conduct accumulates.** If the employee is reporting the bad conduct, then so much the worse for them -- they're showing themselves to be the sorts who stand up for themselves and so may be more likely to file a discrimination complaint.
Consider how this dynamic might have played out in Hales' case. Suppose the manager knew that one instance of customer harassment of this sort against Hales would likely not be enough to create any legal liability for Casey's. But if it happened again to Hales, or multiple times, then Casey's may well be on the hook. What are the options? Well, one is to take concrete steps to protect Hales from this predatory customer (e.g., banning him from the store) and harassment more generally. But that's difficult, and maybe expensive, and it alienates a customer! So option two is just to fire Hales. If you fire her now, the legal case is nipped in the bud. Problem solved.
And make no mistake: this set of perverse incentives will fall heaviest on the most vulnerable employees. It is entirely predictable that the employees most likely to be subjected to repeat instances of sexually aggressive, harassing conduct are young, those working overnight shifts, racial minorities, gender-nonconforming, and the like (Hales met at least the first two of these). Hence, it is these employees who are most likely to be -- and be perceived as -- potential "repeat victims". And that means they are the most likely to encounter "preemptive strike" discrimination -- a form of employment discrimination that does not just avoid legal accountability, but in many ways is the product of the (exceptions to) antidiscrimination law itself.
So the obvious reform is to make clear that Title VII retaliation protections extend to cases of opposition to sexual or racial misconduct even where the practices would not themselves (yet) rise to being independently legally actionable.
But it's also the more straightforward case that what Hales really needed here was a union. It is very difficult to craft legal rules which do not create some sets of bad incentives or which a clever employer cannot game to their advantage. Given who writes laws (political elites) and who interprets them (legal elites), these unanticipated consequences are unlikely to be randomly distributed -- they will track the usual lines of social power and advantage.
Hence, what Hales really needs is someone whose job it is to be in her corner, a body which can protect her from such arbitrary employer action in the particular case even when the general law couldn't shield her. In other words, she needs a union.
* Retaliation jurisprudence generally envisions "opposition" to mean something like reporting the conduct to company officials or public authority officials. Nonetheless, I'd be inclined to say that physically resisting harassment in the workplace should qualify as "opposing" that conduct. But there remains the separate problem illuminated by the Jordan case: where the conduct "opposed" does not alone suffice to create a "severe and pervasive" hostile work environment (as it almost never will in the first instance), then no action by the employee -- whether it's filing a report or physical resisting her harasser -- would be covered under anti-retaliation protections.
** A similar dynamic sometimes emerges in the labor law context, where employees are protected insofar as they engage in "concerted action". On face, this gives employers who see the potential for emergent concerted labor action an incentive to fire the source employee before any organization can begin. But unlike in the discrimination-retaliation context, both courts and the NLRB have concluded that such "preemptive strikes" also violate labor law, even where they come before any conduct that itself would qualify as "concerted action" and even where they successfully preclude any such action from later manifesting.
Lauren Hales was an eighteen year old employee working the graveyard shift at Casey's General Store. At 1:45 AM, a customer came in and starting making sexually suggestive comments towards her. In an attempt to avoid the man, Hales stepped outside to take a cigarette break. The man followed her, blocked the entrance to the store, and continued making sexual remarks.
Hales, who had previously been sexual assaulted, told the guy to "back off". The customer replied "what are you going to do about it?", at which point Hales extended her cigarette to ward him off. Instead, the customer stepped towards Hales, burning his arm on her cigarette in the process.
The next day, the customer complained to a Casey's manager that Hales had burned his arm. The next time Hales reported to work, a manager asked her if "anything out of the ordinary" happened on her previous shift. She forthrightly reported the cigarette incident, but said she had done it in self-defense.
Hales was then terminated.
She sued, alleging sexual harassment and retaliation -- and the Eighth Circuit just rejected both of those claims. The harassment claim failed because the customer's conduct wasn't "severe or pervasive" enough to constitute sexual harassment as a matter of law (the Eighth Circuit apparently hasn't decided whether a company can be held liable for harassment done by a customer, but it assumed for sake of argument that it could). The retaliation claim was rejected because it was filed too late, but apparently the district court had also indicated it should fail because Hales was not engaged in protected activity under Title VII.
Here's the thing: I'm not sure this decision is wrong as a matter of (current) law. The "severe and pervasive" threshold necessary to make out a harassment claim is extremely (I'd say ludicrously) high, and I know of no case law which addresses self-defense steps as a form of "opposing" harassment in the workplace.*
But even if the case "rightfully" lost, all that demonstrates is that antidiscrimination law -- even when "correctly" applied -- isn't sufficient to protect vulnerable workers (even from discrimination).
In fact, the structure of antidiscrimination law in many ways encourages employers like Casey's to act in precisely this fashion -- terminating employees who are the victims of sexual harassment (whether by customers or coworkers) as a "preemptive strike" before they're able to put together a legally cognizable claim of discrimination. Even if one doesn't think that antidiscrimination law should expand to create liability for a single case of customer harassment, there's surely something perverse about it allowing (or even encouraging!) a young woman to be fired because she refused to tolerate a customer harassing her.
When I read this case, it reminded me of one of the very first employment discrimination cases I read which got me hot under the collar -- Jordan v. Alternative Resources Corp. In that case, Jordan -- in accordance with company policy -- reported a coworker who, while watching news coverage that two Black criminals had been arrested, exclaimed "[t]hey should put those two black monkeys in a cage with a bunch of black apes and let the apes fuck them." His supervisor took decisive action ... against Jordan: changing his work hours to less desirable times, making derogatory comments towards Jordan, and then -- within a month of the initial complaint -- firing Jordan. Jordan sued, claiming his termination was retaliation for filing his complaint.
Title VII only protects against retaliation if you're opposing an act covered under Title VII. In Jordan, the Fourth Circuit concluded that the single racist remark Jordan reported could not alone have sufficed to create legally actionable harassment (again, not being "severe or pervasive" enough to qualify), which means he was not "opposing" covered conduct, which means that his company was not retaliating against him as a matter of law (even though, again, company policy required that Jordan file his complaint).
Jordan argued that his complaint should have been protected because it covered action that, if left unabated, would have eventually ripened into unlawful harassment. The court refused to make the extension, and the result is an obvious Catch-22: Jordan has to report conduct that is not "yet" harassment in order to obey company policy (and preserve a potential future harassment claim), but he can be retaliated against for filing the reports.
But there's a deeper problem in the incentive structure this rule creates: As soon as an employer begins to observe incipient harassing conduct that has not (yet) risen to be legally actionable, it probably should terminate the victim before a sufficient record of wrongful conduct accumulates.** If the employee is reporting the bad conduct, then so much the worse for them -- they're showing themselves to be the sorts who stand up for themselves and so may be more likely to file a discrimination complaint.
Consider how this dynamic might have played out in Hales' case. Suppose the manager knew that one instance of customer harassment of this sort against Hales would likely not be enough to create any legal liability for Casey's. But if it happened again to Hales, or multiple times, then Casey's may well be on the hook. What are the options? Well, one is to take concrete steps to protect Hales from this predatory customer (e.g., banning him from the store) and harassment more generally. But that's difficult, and maybe expensive, and it alienates a customer! So option two is just to fire Hales. If you fire her now, the legal case is nipped in the bud. Problem solved.
And make no mistake: this set of perverse incentives will fall heaviest on the most vulnerable employees. It is entirely predictable that the employees most likely to be subjected to repeat instances of sexually aggressive, harassing conduct are young, those working overnight shifts, racial minorities, gender-nonconforming, and the like (Hales met at least the first two of these). Hence, it is these employees who are most likely to be -- and be perceived as -- potential "repeat victims". And that means they are the most likely to encounter "preemptive strike" discrimination -- a form of employment discrimination that does not just avoid legal accountability, but in many ways is the product of the (exceptions to) antidiscrimination law itself.
So the obvious reform is to make clear that Title VII retaliation protections extend to cases of opposition to sexual or racial misconduct even where the practices would not themselves (yet) rise to being independently legally actionable.
But it's also the more straightforward case that what Hales really needed here was a union. It is very difficult to craft legal rules which do not create some sets of bad incentives or which a clever employer cannot game to their advantage. Given who writes laws (political elites) and who interprets them (legal elites), these unanticipated consequences are unlikely to be randomly distributed -- they will track the usual lines of social power and advantage.
Hence, what Hales really needs is someone whose job it is to be in her corner, a body which can protect her from such arbitrary employer action in the particular case even when the general law couldn't shield her. In other words, she needs a union.
* Retaliation jurisprudence generally envisions "opposition" to mean something like reporting the conduct to company officials or public authority officials. Nonetheless, I'd be inclined to say that physically resisting harassment in the workplace should qualify as "opposing" that conduct. But there remains the separate problem illuminated by the Jordan case: where the conduct "opposed" does not alone suffice to create a "severe and pervasive" hostile work environment (as it almost never will in the first instance), then no action by the employee -- whether it's filing a report or physical resisting her harasser -- would be covered under anti-retaliation protections.
** A similar dynamic sometimes emerges in the labor law context, where employees are protected insofar as they engage in "concerted action". On face, this gives employers who see the potential for emergent concerted labor action an incentive to fire the source employee before any organization can begin. But unlike in the discrimination-retaliation context, both courts and the NLRB have concluded that such "preemptive strikes" also violate labor law, even where they come before any conduct that itself would qualify as "concerted action" and even where they successfully preclude any such action from later manifesting.
Labels:
employment discrimination,
judiciary,
labor,
Sexism,
sexual harassment,
unions
Sunday, April 08, 2018
You Don't Need Hyperbole When The Truth Works Fine
International Law Professor Yuval Shany has an outstanding post working through the legal use-of-force issues surrounding the Gaza protests at the Israel/Palestine border. The reason that it's outstanding is that it takes seriously the fact that some of the protesters may be violent and may be trying to breach the border -- it isn't just people randomly waving flags. Many pro-Israel commentators have made this observation and acted as if that were that -- a dismissal made easier when pro-Palestinian voices have acted as if there was no component of armed violence in the equation at all.
Yet my instinct was that, even if there were actual attempts to cross the border or even some use of violent force (e.g., stone throwing), this wouldn't necessarily suffice to justify the use of lethal force by IDF. Shany's post explains why in detail, fully attentive to the actual security concerns faced by Israel, and that makes it far more powerful as a critique of the IDF's conduct -- conduct that seems very likely to have violated international law -- than the median post which treats those concerns as non-existent.
Of course, it may seem silly to go into a fine-grained, nuanced explanation of why IDF use-of-force practices on the Gaza border have been unlawful when Avigdor Liberman is explicitly saying that every single human being in Gaza is a valid target for lethal force.
More and more, it seems that the IDF prefers calling itself "the most moral army in the world" to actually acting like "the most moral army in the world." The way you become and then stay a "moral" army is via discipline, and discipline means actually investigating and punishing potential violations of the rules of armed conflict. But Liberman refuses to even countenance an investigation -- well, unless it's of human rights groups asking that soldiers not shoot unarmed civilians across the border. A culture of impunity will yield a culture of violation -- there is nothing in the Israeli or Jewish soul that renders us immune from the general rules of human behavior.
Yet my instinct was that, even if there were actual attempts to cross the border or even some use of violent force (e.g., stone throwing), this wouldn't necessarily suffice to justify the use of lethal force by IDF. Shany's post explains why in detail, fully attentive to the actual security concerns faced by Israel, and that makes it far more powerful as a critique of the IDF's conduct -- conduct that seems very likely to have violated international law -- than the median post which treats those concerns as non-existent.
Of course, it may seem silly to go into a fine-grained, nuanced explanation of why IDF use-of-force practices on the Gaza border have been unlawful when Avigdor Liberman is explicitly saying that every single human being in Gaza is a valid target for lethal force.
"It has to be understood that there are noThe strike-out is there because Liberman claims he's been mistranslated in the use of the word tamim. But I don't think it materially alters the point he was making, which more-or-less explicitly labels the entire Gaza population as members of a hostile military force who are therefore valid targets for lethal force.innocent[naive] people in Gaza," Liberman added. "Everyone is affiliated with Hamas, they are all paid by Hamas, and all the activists trying to challenge us and breach the border are operatives of its military wing."
More and more, it seems that the IDF prefers calling itself "the most moral army in the world" to actually acting like "the most moral army in the world." The way you become and then stay a "moral" army is via discipline, and discipline means actually investigating and punishing potential violations of the rules of armed conflict. But Liberman refuses to even countenance an investigation -- well, unless it's of human rights groups asking that soldiers not shoot unarmed civilians across the border. A culture of impunity will yield a culture of violation -- there is nothing in the Israeli or Jewish soul that renders us immune from the general rules of human behavior.
Labels:
Avigdor Lieberman,
Gaza,
international law,
Israel,
Palestine,
violence,
war crimes
A Tale of Two Harassers
Jill Filopovic points out the key differences between Democrats and Republicans on sexual harassment and misconduct within their ranks.
It isn't that Republicans perpetuate it and Democrats don't. Both parties have their share of wrongdoers.
The difference is that Democrats -- slowly, fitfully, imperfectly -- are beginning to hold their abusers to account. While Republicans, by and large, continue to shield the predators in their ranks (starting with the one in the Oval Office). There's a reason, Filopovic notes, why Republicans still point to Chappaquiddick and the Bill Clinton affairs -- rounding past 20 years ago at this point -- as their preferred form of whataboutery. In the more recent major cases, Democrats have been much stronger, while Republicans still prefer to protect the boys club.
We saw a great example of this recently in Colorado: A Democrat and a Republican in the state legislature were accused of sexual harassment (the former was a member of the state house, the latter of the state senate). In both cases, an independent investigator substantiated the allegation. The Democrat was expelled, after refusing calls from his own party leaders to resign. Indeed, every single Democratic member of the house voting to do so (Republicans split 16-9 in favor of expulsion).
The Republican? He enjoyed the firm support of his caucus leader, and when Democrats forced a vote on the issue, he kept his job -- with all but one Republican backing him against a motion to expel.
It isn't that Republicans perpetuate it and Democrats don't. Both parties have their share of wrongdoers.
The difference is that Democrats -- slowly, fitfully, imperfectly -- are beginning to hold their abusers to account. While Republicans, by and large, continue to shield the predators in their ranks (starting with the one in the Oval Office). There's a reason, Filopovic notes, why Republicans still point to Chappaquiddick and the Bill Clinton affairs -- rounding past 20 years ago at this point -- as their preferred form of whataboutery. In the more recent major cases, Democrats have been much stronger, while Republicans still prefer to protect the boys club.
We saw a great example of this recently in Colorado: A Democrat and a Republican in the state legislature were accused of sexual harassment (the former was a member of the state house, the latter of the state senate). In both cases, an independent investigator substantiated the allegation. The Democrat was expelled, after refusing calls from his own party leaders to resign. Indeed, every single Democratic member of the house voting to do so (Republicans split 16-9 in favor of expulsion).
The Republican? He enjoyed the firm support of his caucus leader, and when Democrats forced a vote on the issue, he kept his job -- with all but one Republican backing him against a motion to expel.
Labels:
Colorado,
Democrats,
Republicans,
sexual harassment
Subscribe to:
Posts (Atom)