How to Turn Law into Code with Tom Barraclough

Hamish and Tom have co-authored the Draft New Zealand API Standard.

And this thing here... which is a paper on radical full-stack digital legal systems.

Is this the one that you are about to publish in Cambridge?

It's been accepted with revisions to the Cambridge Forum on AI journal, which I'm excited about.

And they've also just had a paper published in the, no, you had a paper in the MIT Computational Law Review and Deloitte is citing that in their Global Trend on Digital Government papers?

Yeah, something like that, yeah.

You're going to make us work really hard today because people who know, people with legal degrees, speak in a very specific way, or at least the words make sense, and we're a little bit flippant with our language.

Even to the point where I loved the part in your paper where you talk about the difference between a developer and a programmer.

I don't know if this is news to you guys.

It is now.

I'm going to get called out by a bunch of developers.

I remember as someone who

does the code, but when you develop inside a system, you're thinking about the development of what you're coding inside a larger tranche of work.

Is that a fair...

We cited somebody else on it, so it's not an original take from me, but essentially it's like you're either on the tools or you're doing the big picture thinking about how everything's meant to work and then doing a little bit of on the tools stuff.

We would call

that architect developer.

Yeah, I mean, you certainly can.

But it's a

colloquialism.

define like the divisions make sense and you could allocate those names to those like those divisions i wouldn't say that they are generically accepted as definitions of those words i

think it's in there in the context of like um you know what does an llm do as well right so it's like it can produce an

llm do wow We got 90 minutes to go.

Let's

presume our audience is at least up to date on that.