Showing posts with label law. Show all posts
Showing posts with label law. Show all posts

Thursday, May 28, 2009

The Sotomayor Nomination

Yesterday, I came across this in an opinion piece by Ilya Shapiro posted on cnn.com, criticizing President Obama's nomination of Judge Sonia Sotomayor to the Supreme Court:

[I]n over 10 years on the Second Circuit, she has not issued any important decisions or made a name for herself as a legal scholar or particularly respected jurist. In picking a case to highlight during his introduction of the nominee, President Obama had to go back to her days as a trial judge and a technical ruling that ended the 1994-95 baseball strike.

Moreover, Sotomayor has a mixed reputation among lawyers who have practiced before her, some questioning her abilities as a judicial craftsman, others her erratic temperament, according to a piece by Jeffrey Rosen in The New Republic, which itself has come in for criticism.

Such anecdotal criticism is to be taken with a grain of salt -- while Justice Antonin Scalia's bench-side manner is more vinegar than honey, even his detractors recognize his brilliance -- but it does need to be investigated. So, too, do certain statements she made in presentations at Berkeley and Duke, respectively, the former arguing that a Latina necessarily sees the law differently than a white man, the latter suggesting that, at least to some degree, judges make rather than interpret law.
Am I correct in reading this to mean that Shapiro's primary beef with Sotomayor is her lack of "brilliance"? I mean, he shrugs off criticisms of her demeanor (apparently on the grounds that any failing of Antonin Scalia's must not be a failing at all), but huffs and puffs that she is no "legal scholar," "respected jurist," or "judicial craftsman." Seriously, how important is brilliance?

Here's a lesson from the real world and the practice of law: past a certain point, additional intelligence provides only short-term advantages. Being smart means you'll pick up the concepts more quickly than others. It means you might be able to come up with cleverer or more intricate arguments, more quickly. But over the long haul, those benefits never trump experience in the trenches. Yes, the Supreme Court is a very important post, and an impressive intellect is an asset; but an astounding intellect is unnecessary.

Secondly, there seems to be something hypocritical (or at least dissembling) about Shapiro's admonition that Sotomayor "has not issued any important decisions or made a name for herself as a legal scholar or particularly respected jurist." To me, this reads as follows: "Judge Sotomayor has failed to leave a satisfactory smoking gun evidencing her liberal activism, which makes my job difficult, since I'm supposed to call her a liberal judicial activist. Therefore, I will paint her failure to stake out such liberal positions as evidence of her intellectual lethargy." In other words, had Sotomayor staked out any clever, novel, or interesting legal positions, Shapiro would be criticizing her for having taken those positions, instead of criticizing her, as he does here, for not having taken them.

Thirdly, Shapiro criticizes Sotomayor for commenting that judges make rather than interpret the law. If you read Shapiro's bio, you will see that he is a lawyer with an impressive-sounding resumé. This is surprising, because he is apparently quite a dim bulb himself. I attended a state law school, where I was taught by outspoken liberals and outspoken conservatives. Not one of them, regardless of their political persuasion, would have denied that in certain circumstances, a judge has the responsibility to make the law. "Interpreting, not making, the law," is something the public likes to hear about its judges, but it has never been the whole story.

Imagine this scenario: a criminal defendant has been tried in state court and found guilty of first degree murder. The jury deliberates, and votes 11-1 to impose the death penalty. A state statute provides that an 11-1 vote is all that is necessary to impose the death penalty. The defendant objects, saying that the state statute violates the Due Process clause of the Fourteenth Amendment, which ought to be interpreted to require unanimity in order to impose the death penalty. All the Due Process clause says is "No State shall... deprive any person of life, liberty, or property, without due process of law." So which is it? Does the Due Process clause require unanimity or is 11-1 good enough? Either answer is plausible, but you can't support either one just from reading the Due Process clause. Say yes or say no, but your decision is not extrapolated from the meaning of the phrase "due process"; your decision gives meaning to the phrase "due process."

The take-away point is this: when the drafters of the Constitution or the legislation punt, the judiciary has to pick up the ball.

Lastly (for now), Shapiro criticizes Sotomayor for remarking that a Latina and a white man necessarily view the law differently. I actually can join Shapiro in being a little riled by this comment. Obviously she's playing to crude racial stereotypes here. Behind it is something like the ethnic imaginings typified in Jennifer Lopez romantic comedies: Latinas are all sassy hotel maids, and white men are all running for the U.S. Senate. You might as well say that black men and Sicilians necessarily have different views on the law—but then how do you explain Justices Thomas and Scalia? These are oversimplifications that should make us all blush, and frankly they're offensive.

On the other hand, by adding a little nuance, I don't think Sotomayor is very far from the truth. I think it's true to say that there are a lot of factors that influence one's view of the law (upbringing, religion, socioeconomic status, etc.), and many of those factors, statistically speaking, break along ethnic, racial, and gender lines. Because I am charitably-inclined, I'll spot her the benefit of the doubt, and assume that Sotomayor's comment was just ill-advised shorthand for the more nuanced version I've put forth.

Friday, March 13, 2009

Bride of Pseudoscience

It's in my nature neither to pay attention to, nor to write about stories as sordid and rubbernecky as this Rihanna-Chris Brown domestic violence story. But upon encountering this gem of a study, I couldn't help but bring it to your attention for your collective ridicule.

The Boston Public Health Commission surveyed 200 Boston youths between ages 12 and 19, "using the Chris Brown-Rihanna case to gauge their attitudes toward teen dating violence." All of the study participants had heard about the incident. Here are some of the results:
  • 71% said arguing was a normal part of a relationship
  • 44% said fighting was a normal part of a relationship
  • 51% said Chris Brown was responsible for the incident
  • 46% said Rihanna was responsible for the incident
  • 52% said both individuals were to blame for the incident, despite knowing at the time that Rihanna had been beaten badly enough to require hospital treatment
  • 35% said the media were treating Rihanna unfairly
  • 52% said the media were treating Chris Brown unfairly
A few of these numbers are troubling. For example, how is it possible for 51% to think Brown is responsible, and for 46% to think Rihanna is responsible, but somehow, for 52% to think both are to blame? Mathematically and logically, it's impossible for more people to affirm the proposition "A & B" than the proposition "A." Does this turn on a subtle connotative difference between "responsibility" and "blame"? Or did the interviewers just ask one too many questions?

Secondly, how is the extent of a person's injuries relevant to determine their responsibility for them? I am right in reading that implication into the fifth statistic, aren't I? I didn't have to go to law school to figure out that the two issues are independent, but I did gor to law school, and we had this pointed out to us a lot of times in Torts. Just commonsensically though, if you step off the curb in front of an oncoming car, your injuries are your responsibility whether the vehicle runs over your foot and breaks your toe, or whether it sends you flying twenty yards and lands you in a full body cast. Liability and damages are independent issues.

Thirdly, and more in line with the presumed intent of the study, who are these 98 idiotic Boston teenagers wandering the streets thinking that a person isn't really to blame if he beats another person so badly that they wind up in the hospital? Are you kidding me? Newsflash, in case any of you happen to be reading: you actually are in control of whether or not you curl your hand into a fist, and hurl it with a high velocity into another person's cheekbone. Strange but true.

As irate as I am about this last statistic, you'd think somebody in the media would be talking about it as well. Wrong. See here and here. What's the most cited statistic culled from the study? I thought you'd never ask:
Of those questioned, ages 12 to 19, 71 percent said that arguing was a normal part of a relationship; 44 percent said fighting was a routine occurrence.
This is the news that has us fretting thusly?:
The results of the survey, conducted by the Boston Public Health Commission across the city and equally among boys and girls, are startling for local health workers who see a generation of youths who seem to have grown accustomed, even insensitive, to domestic violence."

I think you'd have to be pretty jaded if you weren't startled by it," said Casey Corcoran, director of the health commission's new Start Strong program.
I'm appalled. I'm appalled by the implication of these supposedly responsible adults that it is not "normal" to "argue" when you're in a relationship. Conflating disagreement with domestic abuse? Somebody should be ashamed. Woe to the teenager who buys into this crock of shit.

"Fight"? I just can't get too excited about 44% of youth thinking it's normal to "fight" with your significant other, in light of how broad the meaning of "fight" can be. It runs the gamut from simple disagreement, to heated argument, to knock-down-drag-out, to hurling a vase at the wall, to giving your better half two black eyes, and beyond. This continuum spans both acceptable and unacceptable behavior, so it's not very surprising that some kids think fighting is normal. If 44% had said that "physical violence" was normal in a relationship, I could see myself joining the chorus. But that's not what happened here. This study is plainly the unholy spawn of pseudoscience and tabloid publishing, so why are there people taking it seriously?

Monday, February 16, 2009

Puzzling Over Some Wacky Ideas about Teenagers, Sex, Technology, and the Law

For as long as I have been a reader of Slate, which probably goes back to around 2001, I have been a fan of Dahlia Lithwick's writing for the online magazine. Even before I'd settled on attending law school after graduation from college, I'd long enjoyed her Supreme Court Dispatches series, which summarized the facts of many of the more notorious cases on the Court's docket, the legal issues attending thereto, and often included transcriptions of the more raucous parts of the oral arguments. Good, good fun, to watch the Court, and especially to do so in the company of such an astute and professional Court-watcher as Lithwick.

Lately though, Lithwick's columns are falling short. A lot of her recent articles on Slate have been cross-published in Newsweek, and those articles have proven particularly lackluster. This weekend, she weighed in on what has become a trend in adolescent circles, namely "sexting," which apparently means taking nude photographs of oneself and electronically transmitting them to other teens. In a number of cases cited in the article, senders and recipients of the sext messages have been charged with crimes related to child pornography. Lithwick forcefully argues that such charges are inappropriate.

We'll assume for the sake of argument that the photographs in question actually qualify as prohibited child pornography in the prosecuting jurisdictions. It turns out though that this assumption may not be warranted in all cases. For instance, in Louisiana, the crime of pornography involving juveniles is governed by La. R.S. 14:81.1. Under that statute, a depiction of "sexual conduct" is required in order to cross the threshold of criminality, and "sexual conduct" is defined as "actual or simulated sexual intercourse, deviate sexual intercourse, sexual bestiality, masturbation, sadomasochistic abuse, or lewd exhibition of the genitals." From this language, it's not clear that a simple nude photograph would be covered; cases would presumably turn on how "lewd" a particular exhibition of the genitals might be.

Anyway, like I said, let's assume that the jurisdictions in question have broader anti-porn laws, or that the photos forming the basis for prosecution are particularly "lewd." Why then should they not be prosecuted? Lithwick can speak for herself:
One quick clue that the criminal justice system is probably not the best venue for addressing the sexting crisis? A survey of the charges brought in the cases reflects that—depending on the jurisdiction—prosecutors have charged the senders of smutty photos, the recipients of smutty photos, those who save the smutty photos, and the hapless forwarders of smutty photos with the same crime: child pornography. Who is the victim here and who is the perpetrator? Everybody and nobody.
Lithwick seems to be suggesting that, in these limited circumstances, child porn is a victimless crime. Of course, you could point to the analogous case of a drug deal: both the seller and the buyer can be charged with a crime. It's equally difficult in that case to identify a "victim," but nobody seriously thinks that a clearly identifiable "victim" is a prerequisite to a certain act being declared criminal. In the case of both illegal drugs and child pornography, the justification for criminalization is the same: when certain revenue streams cause aggregate damage to the physical, mental, or sexual health of the public, those revenue streams ought to be shut down.

Lithwick quotes a police captain in a Pennsylvania case, who argues that the prosecutions are justified, saying, "Once it's on a cell phone, that cell phone can be put on the Internet where everyone in the world can get access to that juvenile picture." She then trivializes his argument, writing:
The argument that we must prosecute kids as the producers and purveyors of kiddie porn because they are too dumb to understand that their seemingly innocent acts can hurt them goes beyond paternalism. Child pornography laws intended to protect children should not be used to prosecute and then label children as sex offenders.
Parenthetically, I'll admit that Lithwick is right on when she says that registration as a sex offender would be an inappropriate punishment for teenage sexting. Those registries are supposed to identify criminal sexual deviants, and whether it's good behavior or bad, nobody ought to maintain that the urges that lead to teen-to-teen sexting are anything other than mainstream.

But again, Lithwick's rush to identify the victim throws her off the scent of what's really going on here. This is not an exercise in paternalism meant to protect the interests of emptyheaded would-be teen sexters. Child porn statutes are meant to shut down commercial activity in contraband, and it is reasonable in that light to enact laws that would curtail production of contraband, including small-scale production.

And besides, the prosecuted teens will ordinarily be benefited by the same procedural safeguard afforded to minors generally in the legal system: prosecution before a specialized juvenile court, with relaxed formalities. Imagine yourself as the juvenile judge before whom a sexting case is brought. You have wide latitude in terms of punishment. Do you really want to put a teen sexter in juvy, much less in prison? No! Your role is the same as it is in the vast majority of other juvenile prosecutions: to ensure the offenders understand the gravity of the situation, the reasons why their conduct is prohibited, and to scare them a little bit. Then you assign them a few hours of community service. In other words, teenagers are already benefited by regulations meant to ensure that their punishment reflects their relative level of informal culpability.

But here's where Lithwick completely loses me, and it's a matter of sort of general penology, rather than something specific to sexting:
Many other experts insist the sexting trend hurts teen girls more than boys, fretting that they feel "pressured" to take and send naked photos. Yet the girls in the Pennsylvania case were charged with "manufacturing, disseminating or possessing child pornography" while the boys were merely charged with possession. This disparity seems increasingly common. If we are worried about the poor girls pressured into exposing themselves, why are we treating them more harshly than the boys?
Allow me to retort with an example from physics. Suppose 10 pounds of force is being applied to an object, but you want the object to stay put. What should you do? Apply 10 pounds of force in the opposite direction. But if 100 pounds of force is being applied, 10 pounds won't be enough; instead you should apply 100 pounds. In other words, if you want to curtail girls sending naked pictures of themselves to boys, and they feel intense peer pressure to do so, a seemingly plausible course of action would be to push back harder, by increasing the applicable punishment to such an extent that it balances or overcomes peer pressure.

Now obviously I make no claims to expertise in child psychology, and can't vouch for whether the push-pushback illustration accurately models a workable incentive structure for teenage girls thinking about sex. But it passes the smell test anyway. Even if it's wrong, it's at least on the side of common sense, so that I think anyone who would take the contra bears the burden of showing why such an incentive structure won't work. Certainly it's not as mystifying as Lithwick seems so hellbent on implying.

But then again, maybe Dahlia's right. I mean, gang initiates feel intense peer pressure to commit murder. So maybe we shouldn't be so hard on them.

Wednesday, January 28, 2009

Congressional Representation for D.C.: Why the Constitution isn't Really such a Big Problem

The District of Columbia presently has no representation in the Congress of the United States. Why not? Because of the Constitution. Art. I, Sec. 2 of our founding document provides:

The House of Representatives shall be composed of Members chosen every second Year by the People of the several States...
Since D.C. is not a state, its people are not constitutionally authorized to elect a member to the House of Representatives. (Art. 1, Sec. 3 makes the same rule applicable to the Senate). If you wonder why this is such an affront, think about every income tax increase, declaration of war, imposition of the draft, etc., in the history of the United States, and recall that the residents of D.C. had no voice in the authorizing legislation, but found themselves just as subject to it as did the citizens of any state. It's practically imperialistic.

There is now a bill in the works to allocate one seat in the House of Representatives to D.C. (No plans for the Senate yet, apparently). The problem is that the bill is almost certainly unconstitutional. Like I pointed out above, the Constitution says if you're not a state, you can't be represented in the House. Not even an act of Congress can change that. It will take a constitutional amendment to properly get D.C. into Congress, just like it took the Twenty-Third Amendment to allow its residents to vote for President.

(There is an interesting Supreme Court Case, Tidewater, holding that Congress could constitutionally treat D.C. as a state for purposes of diversity jurisdiction, even though the text of the Constitution says that diversity jurisdiction only applies to cases and controversies "between Citizens of different States." Tidewater is probably distinguishable though, because the question involved there was not nearly as politically fraught as this one is. A court has inherent authority to determine the limits of its jurisdiction, which is all that the Supreme Court did in Tidewater; courts will tread much more lightly on the turf of the legislative branch.)

Anyway, I was reading today an argument from someone fretting the unconstitutionality issue, but urging the passage of the legislation anyway. His argument was that although the measure would be overturned in court, the legal turmoil would publicize the plight of D.C. residents, laying the groundwork for a later constitutional amendment. I have a better idea. Pass the unconstitutional law and don't sweat it; it will not be overturned anytime soon.

Just because a law is unconstitutional doesn't mean that Joe Schmoe can file a petition in U.S. District Court to have it declared unconstitutional. You have to overcome an initial showing that you have "standing." In general, that means that you have to show that the unconstitutional law is causing you a particularized harm, and that an order from the court will be effective to cease that harm. Now I ask you, who has standing to argue in court that the D.C. representation act ought to be declared unconstitutional? I've come up with two scenarios, both somewhat implausible.
  1. Imagine that after the D.C. Representative is seated, he votes to enact a new federal criminal statute. The measure passes the House by one vote, is passed by the Senate, and signed by the President. Later on, a criminal defendant is indicted under the new measure. The defendant brings a motion to quash the indictment, arguing that he didn't violate the law because there was no law; the bill was never properly passed by the House of Representatives. It was only considered to have passed because of the improperly seated Representative from D.C., whose vote should not have been counted. Now, the issue really is whether the law authorizing a seat in the House for D.C. is constitutional, and the criminal defendant can clearly meet the burden of standing. The situation is implausible because it relies on the bill passing by one vote; otherwise it makes no difference how the Representative from D.C. voted.
  2. The Constitution gives the members of each house the authority judge the "Qualifications of its own Members" (Art. 1 Sec. 5). They can and do sometimes refuse to seat members, as you may recall from part of the Rod Blagojevich scandal. It's not beyond the realm of possibility that the House could refuse to seat a Representative from D.C. on the grounds that his election would have been unconstitutional. If they do so, his recourse is to sue in federal court to have his election declared valid, at which point, the court will have to decide the issue of whether the statute authorizing his election was constitutional. The reason this scenario is implausible is that, assuming the D.C. Represenatation statute passed the House in the first place, it's doubtful that the House members would then turn around and refuse to seat the elected representative. It would take a big shift in the makeup of the House for that turnaround to occur; by the time it does, the congressman from D.C. may already be pretty well entrenched, and the political fallout from the challenge might outweigh the political gain.

Pass this statute because it's the right thing to do for the residents of D.C., and because it stands to actually do some good long before anybody racks up the standing to have it declared unconstitutional.