ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Miscellaneous Blogs -> Law & Humanities Blog

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Miscellaneous

: Law & Humanities Blog

Why Lawyers Should Read Shakespeare

ADVERTISEMENTS
Michael P. Maslanka, the managing partner of Ford & Harrison in Dallas, has this article on Law.com about why lawyers should read Shakespeare. The article begins:

Why do students still read Shakespeare? A conspiracy of finger-wagging, we-know-what's-best-for-you high school English teachers? No. It's his empathetic powers, making people see ourselves as we are -- rationalizations not permitted.

Shakespeare has much to teach lawyers. Eschewing Judge Judy, his questions are penetrating: How should judges go about judging? Does the rule of law matter? Are mercy and justice mutually exclusive, or are they complementary?

The article goes on to discuss Shakespeare's play, Measure for Measure.

Full post as published by Law & Humanities Blog on August 19, 2008 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Lawsuits and Settlements

Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.0163 secs (new cache)