It was never going to be one-and-done: thinking evolved, CLMs and GenAI blew up, and the team kept figuring things out. The second edition is being published on 24 June, with fresh content on purpose, ideal behaviours, and why relationships matter most (plus AI!).
The real Philosopher's Stone of legal AI is teaching the machine to reason about whether things are important enough to raise with the other side.
Most people mistakenly think that legal AI should spot and raise every issue, every time.
When we make decisions based on AI output volume alone, ignoring everything else that goes on during product development, we do more harm than good, to the point where the organization may be better off abandoning AI development entirely. You cannot assess AI "productivity improvements" without looking at the entire product development flow, taken from when it's a gleam in somebody's eye to delivery to customers and beyond. A simple output-volume metric is worthless on its own. You have to consider the entire system.
Goldratt's "The Goal," which I think of as essential reading—knowing that material is a basic software-engineering competence at the level of knowing how to code—addresses exactly this issue. Goldratt talks about robotic automation in a factory damaging overall productivity, but that's exactly the problem we're dealing with when we use robotic (AI) code generators. Automating a sub-process does nothing but jack up operating expenses unless it addresses a bottleneck in the overall development flow. Coding has never been the bottleneck.
AI, as often used, does nothing but increase inventory (work done that generates no revenue), and as the inventory piles up, it encourages shortcuts (e.g., inadequate review and testing) that disrupt the flow and damage overall productivity.
People do say that "AI creates challenges," but we have not even scratched the surface of how to address those. In the meantime, we make knee-jerk adjustments to our process that damage overall productivity, and given that most organizations are incapable of accurate self-assessment, that goes entirely unnoticed. There are things we can do to get the situation under control. For example: human-created software architecture can be used as a constraint on the AI, working in very small batches makes reviews possible, making the feedback loops faster increases the value of the software and makes necessary changes easier. We can analyze literally everything that happens as a product is developed (the "value stream") and optimize the entire process. We can improve development flow to eliminate dependencies and bottlenecks.
We, as an industry, don't seem willing to do any of that, however. We ignore those things at our own peril.
Our yearlong investigation reveals Nigel Farage courting illicit funding as part of a plot to bring foreign money into British politics, orchestrated by his top aides and caught on hidden camera.
2025 is going to be a huge year for AI Agents.
Russell & Norvig recently published this great textbook on Agents!!🤯
Here's what's included:
AI Complete!
Where can you learn about it all?
Your neighborhood Intro #AI course.. (eg. rakaposhi.eas.asu.edu/cse471… )
Many thanks to all the people who have helped me go deeper, including @AdamsDrafting, Chris Butterworth, @CarrNext, Martin Clausen, Douglas E Dawson, Norman Faull, @damienriehl, @EdeStadler, Duc V. Trang, Andy Unger, and @andywishart.
Need to update our list of document automation platforms (pure plays, not CLMs) for our doc auto guide. We still love Docassemble, but what else is out there?
When I was 18 (1989), my father for some reason gave me books by Marshall McLuhan and Charles Handy. They both had a profound impact on my thinking to this day. Give your kids weird books :)
Marshall McLuhan, who died in 1980, was one of the most prophetic thinkers of last century.
When I wrote about him a year ago, I was stunned at the viral response.
The editors at @TheFP asked me to go deeper—and my amazement grew.
Here are 6 astonishing things McLuhan got right about our world: