A little while ago lawyers at Sydney firm Gilbert + Tobin took part in a one-day workshop designed to teach lawyers how to deploy, interact with and design the business logic in smart contracts. The story was carried in the Global Legal Post and Simon Gilchrist, the firm’s innovation officer said:
“These workshops put Gilbert + Tobin at the forefront in terms of capabilities, imagination, and technical understanding of our legal team.”
This is not a particularly new concept, but it still relatively rare. There many different reasons why learning about coding, data and databases is a good thing to do. “Its fun” may not be top of the list. A great way of putting it is from the blog by David Zvenyach:
“…Asking whether lawyers should learn to code is like asking whether lawyers should read fiction… Reading fiction can help a lawyer improve her legal writing. It can help foster greater empathy and understanding of others’ motivations.”
Many years ago, Colin Sutherland QC (who is now the most senior judge in Scotland, the Lord President) gave a talk to solicitor advocates on the importance of written pleadings and in particular the ability to present complex questions clearly and concisely. His advice was simple – read. The more you read, and the wider the range of books that you read, the greater your understanding of the complexity of language. And fundamentally the objective of a contracts lawyer is to capture the parties’ intentions; the objective of a contentious lawyer is to use language to persuade an opponent of the merits of an argument. As an aside, reading older texts can lead to the discovery of strange and wonderful words. My latest discovery is “slobgollion”: “an ineffably oozy, stringy affair, most frequently found in the tubs of sperm, after a prolonged squeezing, and subsequent decanting. I hold it to be the wondrously thin, ruptured membranes of the case, coalescing.” You need to read the rest of Moby Dick to understand the context!
Back to coding. Until you have had the chance to play around with code, it is difficult to visualise the opportunities. Even the simplest of code opens your eyes to the art of the possible. I remember experimenting with the most basic command, and having “Hello World” appear on a web site page. Over the years, exploring HTML, CSS, .asp and SQL took me to the creation of some reasonable complex web sites. Once you understand how data can be structured and then manipulated, the possibilities become clear. The next thing you realise is that a different set of skills come into play – and that for the bigger projects you need the help of mathematicians and coders.
But without that basic background, as Simon Gilchrist puts it, you lack the technical understanding that fuels the imagination.
