Jeremy R. Paul

Jeremy R. Paul (born July 22, 1956), was the Dean of Northeastern University School of Law from 2012 until June 2018.[2]

Jeremy R. Paul
Dean of Northeastern University School of Law
In office
August 2012  June 2018
Preceded byEmily Spieler
Succeeded byJames Hackney
Personal details
BornJuly 22, 1956[1]
New York, New York
NationalityAmerican
Spouse(s)Laurel Leff
Alma materPrinceton University, (A.B., 1978); Harvard Law School, (J.D., 1981).

Education

Paul graduated from Princeton University in 1978 and received his law degree from Harvard in 1981.

Career

Jeremy Paul joined the Northeastern University School of Law faculty as dean in 2012. He teaches Constitutional Law, Property and Jurisprudence. A 1978 graduate of Princeton University, he received his law degree from Harvard in 1981. Before coming to Northeastern, Dean Paul served for 23 years on the faculty of the University of Connecticut School of Law, where he was Dean and Thomas F. Gallivan, Jr. Professor of Real Property Law from 2007 until 2012. Dean Paul served as associate dean for academic affairs at UConn Law from 1999 until 2004, when he was named associate dean for research. Dean Paul previously served as a law clerk to Judge Irving Robert Kaufman of the U.S. Court of Appeals for the Second Circuit;[3] as Professor-in-Residence at the Appellate Staff of the Civil Division of the U.S. Department of Justice and as Assistant to the President of TravelersGroup. Paul has taught at the University of Miami as both assistant and associate professor, and at Boston College Law School as a visiting professor.

Writings

Dean Paul's writings have appeared in the Texas Law Review, the Michigan Law Review, the University of Southern California Law Review, and the Washington Monthly. His writings include (with Michael Fischl) the book Getting to Maybe: How to Excel on Law School Exams [4] and a widely used introduction to legal reasoning titled "A Bedtime Story."[5]

Dean Paul has served on the Board of Directors of the Connecticut Bar Foundation and the Advisory Board of the Connecticut Law Tribune. He is also a former Board Member of the Connecticut Civil Liberties Union.

gollark: I can't easily come up with a *ton* of examples of this, but stuff like generics being special-cased in for three types (because guess what, you *do* actually need them), certain basic operations returning either one or two values depending on how you interact with them, quirks of nil/closed channel operations, the standard library secretly having a `recover` mechanism and using it like exceptions a bit, multiple return values which are not first-class at all and which are used as a horrible, horrible way to do error handling, and all of go assembly, are just inconsistent and odd.
gollark: And inconsistent.
gollark: But... Google is hiring some of the smartest programmers around, can they *not* make a language which is not this, well, stupid? Dumbed-down?
gollark: It has some very nice things for the cloud-thing/CLI tool/server usecase; the runtime is pretty good and for all garbage collection's flaws manual memory management is annoying, and the standard library is pretty extensive.
gollark: I'm not entirely sure what the aim is - maybe they originally wanted to go for highly concurrent systems or something, but nowadays it seems to mostly be used in trendy cloudy things, servers, command line utilities, that sort of thing.

References


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.