/
16.09.2019 at 10:32 am
Cuttings

Legal Practice & Taking From Software Best Practices

My litigation style is gradually taking cues from software engineering best practices.

Or so it seems.

I heavily use Python, Git and Sublime Text in my legal practice. I also apply version control, automation tools, data validation, testing, diagrams/flowcharts, large codebase/text analysis and diffing, structured syntax (like Markdown and YAML), etc. And I write many custom tools or scripts in between, and use libraries from other sub-disciplines (data science tools like Pandas and Numpy, and natural language processing libraries like NLTK).

I use such tools to solve legal problems, for which my usage applies to virtually all aspects of my court work as counsel and/or solicitor.

I understand that what I do is very uncommon for lawyers. But I don't do this just because I 'can'. I do it because I think it's necessary: with these tools I expedite work and remove potentially-costly mistakes; further I reduce my time spent by a factor of 5x of more, easily. (I know, because I've done things the manual way before, in my earlier junior days. And I tracked time to compare.)

All this translates into savings for clients, and less legal labour. And most importantly, free time to do other interesting things.

As such I often suggest to learned friends that they look at and learn these new tools. The ones who try rarely put in the hours to go beyond surface exploration. This means that they then don't see (and can't understand) what the true benefits are.

Most however refuse. "I've no time", or "I'm busy", or "it's too complex" are standard answers.

Those aren't valid excuses. Especially for members of a profession who proudly assert that they are life-long learners.

Lawyers should be savvy. If our old tools are superseded by better, tested and well-engineered tools, with little to no drawback from their use (except perceived complexity), time must be made to learn and adopt them. The best features from other disciplines should also be readily taken if they help us as professionals. After all, doctors, architects and engineers keep up without problems - it's even expected of them to keep up.

If they can keep up, so can we. New tools should not be feared.


Filed under:
#
#
#
Words: 314 words approx.
Time to read: 1.26 mins (at 250 wpm)
Keywords:
, , , , , , , , ,

Potentially related:
  1. Teach Thy Tongue to Say: 'I Do Not Know'
  2. Reflections - 43 Things I Learned or Did In 2019

Other suggested posts

  1. 18.06.2022 at 06:52 pm / Strangling Deeds
  2. 13.08.2020 at 10:00 am / Consenting Pythonic Adults
  3. 20.05.2020 at 01:05 am / A Programmer & His Mechanical Friend
  4. 14.01.2020 at 01:24 pm / Third Time's A Charm
  5. 16.09.2019 at 10:32 am / Legal Practice & Taking From Software Best Practices
  6. 12.07.2016 at 12:00 am / Refunctin' Blocks
  7. 28.06.2015 at 12:00 am / No Social Transformation Without Representation
  8. 31.05.2015 at 12:00 am / Judges Should Not Fear Criticism
  9. 03.07.2013 at 12:00 am / Craft Versus Discipline
  10. 04.07.2012 at 12:00 am / When To Not Use Data Structures/Algorithms
© Wan Zafran. See disclaimer.