{"id":87272,"date":"2023-06-02T10:27:00","date_gmt":"2023-06-02T14:27:00","guid":{"rendered":"http:\/\/danielschristian.com\/learning-ecosystems\/?p=87272"},"modified":"2023-06-02T11:04:20","modified_gmt":"2023-06-02T15:04:20","slug":"the-perils-of-consulting-an-electric-monk-furlong-other-legaltech-related-items","status":"publish","type":"post","link":"http:\/\/danielschristian.com\/learning-ecosystems\/2023\/06\/02\/the-perils-of-consulting-an-electric-monk-furlong-other-legaltech-related-items\/","title":{"rendered":"“The perils of consulting an Electric Monk” [Furlong] + other legaltech related items"},"content":{"rendered":"

The perils of consulting an Electric Monk<\/strong><\/a> — from jordanfurlong.substack.com by Jordan Furlong
\nDon’t blame ChatGPT for the infamous incident of the made-up cases. And don’t be too hard on the lawyer, either. We’re all susceptible to a machine that tells us exactly what we want to hear.<\/em><\/p>\n

\"\"<\/a><\/p>\n

Excerpt:<\/em><\/p>\n

But then the \u201cChatGPT Lawyer\u201d story happened<\/a>, and all hell broke loose on LawTwitter and LawLinkedIn, and I felt I needed to make three points, one of which involves an extra-terrestrial robot.<\/p>\n

My first two points are pretty straightforward:<\/p>\n

    \n
  1. The tsunami of gleeful overreaction from lawyers on social media, urging bans on the use of ChatGPT and predicting prison time for the hapless practitioner, speaks not only to their fear and loathing of generative AI, but also to their desperate hope that it\u2019s all really nothing but hype and won\u2019t disturb their happy\u00a0status quo<\/em>. Good luck with that.<\/li>\n
  2. The condemnation and mockery of the lawyer himself, who made a bad mistake but who\u2019s been buried by an utterly disproportionate avalanche of derision, speaks to the lack of compassion in this profession, whose members should pray that their worst day as a lawyer never makes it to the front page of\u00a0The New York Times<\/em>. There but for the grace of God.<\/li>\n<\/ol>\n

    Are you looking for evidence to support the side that\u2019s hired you? Or are you looking for the truth? Choosing the first option has never been easier. It\u2019s also never been more dangerous.<\/strong><\/span><\/p><\/blockquote>\n

    \n

    As referenced topic-wise by Jordan above, also see:<\/span><\/em><\/p>\n

    A lawyer used ChatGPT to prepare a court filing. It went horribly awry.<\/strong><\/a>\u00a0— from cbsnews.com by Megan Cerullo<\/p>\n

    \n

    What I learned at CLOC 2023<\/strong><\/a> — from alexofftherecord.com by Alex Su
    \nThis week I attended the premier legal operations conference. Here’s what I heard.<\/em><\/p>\n

    Excerpt:<\/em><\/p>\n

    Theme 1: Generative AI isn\u2019t going anywhere<\/strong>
    \nThis was a huge theme throughout the conference. Whether it was vendors announcing GPT integrations, or panels discussing how to use AI, there was just an enormous amount of attention on generative AI. I\u2019m certainly no stranger to all this hype, but I\u2019d always wondered if it was all from my Silicon Valley bubble. It wasn\u2019t.<\/p>\n

    What was driving all this interest in AI? Well, the ubiquity of ChatGPT. Everyone\u2019s talking about it and trying to figure out how to incorporate it into the business. And not just in the U.S. It\u2019s a\u00a0worldwide trend. Word on the street is that it\u2019s a CEO-level priority. Everywhere. So naturally it trickles down to the legal department.<\/p>\n

    \n

    We need to talk about ChatGPT<\/strong><\/a> — from mnbar.org by Damien Riehl<\/p>\n

    Excerpt:<\/em><\/p>\n

    How well do LLMs perform on legal tasks?\u00a0<\/strong><\/h4>\n

    Personal experience and anecdotal evidence indicate that LLMs\u2019 current state provides impressive output in various legal tasks. Specifically, they provide extraordinary results on the following:<\/p>\n

      \n
    • Drafting counterarguments.<\/li>\n
    • Exploring client fact inquiries (e.g., \u201cHow did you lose money?\u201d).<\/li>\n
    • Ideating\u00a0voir dire<\/em>\u00a0questions (and rating responses).<\/li>\n
    • Summarizing statutes.<\/li>\n
    • Calculating works\u2019 copyright expiration.<\/li>\n
    • Drafting privacy playbooks.<\/li>\n
    • Drafting motions to dismiss.<\/li>\n
    • Responding to cease-and-desist letters.<\/li>\n
    • Crafting decision trees.<\/li>\n
    • Creating chronologies.<\/li>\n
    • Drafting contracts.<\/li>\n
    • Extracting key elements from depositions.<\/li>\n<\/ul>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      The perils of consulting an Electric Monk — from jordanfurlong.substack.com by Jordan Furlong Don’t blame ChatGPT for the infamous incident of the made-up cases. And don’t be too hard on the lawyer, either. We’re all susceptible to a machine that tells us exactly what we want to hear. Excerpt: But then the \u201cChatGPT Lawyer\u201d story […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[356,817,482,825,837,830,285],"tags":[],"class_list":["post-87272","post","type-post","status-publish","format-standard","hentry","category-artificial-intelligence-agents-llms-and-related","category-bots","category-intelligent-systems","category-law-schools","category-legal-operations","category-legal-technologies","category-legislation-legislatures"],"_links":{"self":[{"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/posts\/87272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/comments?post=87272"}],"version-history":[{"count":8,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/posts\/87272\/revisions"}],"predecessor-version":[{"id":87295,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/posts\/87272\/revisions\/87295"}],"wp:attachment":[{"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/media?parent=87272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/categories?post=87272"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/danielschristian.com\/learning-ecosystems\/wp-json\/wp\/v2\/tags?post=87272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}