I would argue that this is true of nearly everyone. A small amount of knowledge can go a long way in helping to build simple tools that save a lot of labour.
For anyone else who is thinking about switching careers, this is how I started: At some point during my career as a lawyer I started collecting ideas for a better, more effective way to work as a lawyer. Software could help a lot while doing many administrative tasks and would allow a lawyer to focus on what creates value - giving legal advice, thinking through tough legal problems, negotiating a great outcome for the client... Yet a lot of enterprise software is too hard to grasp, and many lawyers just stick with the old way, doing most things manually (by themselves or have it done by their assistants).
So I started building one MVP, pivoted and now am building a "GitHub for Word". Steep learning curve as a startup founder and well worth giving it a try. If you are interested, check out my project Jules: https://julesdocs.com
What about as a partner?
Worse yet, lawyers have to keep working to continue to receive equity compensation in the overwhelming majority of cases. So you can't retire and continue to make money from your equity stake. You can't even really cut back on the crazy hours. This answer covers it pretty thoroughly: https://www.quora.com/Do-partners-in-law-firms-keep-a-share-...
Can you give a few examples of practical uses of those tools ?
I wrote a short blurb about my experience a little while ago: http://www.cachestocaches.com/2016/2/how-we-teach-programmin...
If anyone there had even the slightest sense of how easy that would be to automate, they'd have saved hundreds of thousands of dollars by paying some random kid $200 to write them a bash script.
That's just a simple example, but I ran into issues like that on a daily basis. Databases full of evidence that were discarded because no one knew how to access them or run queries on them. Whole inboxes of emails in ost files thrown away because no one knew how to open them. Hundreds of hours spent manually reviewing documents when OCR and a decent text search tool could have gotten the same result in minutes. It was just never ending.
Also, there are discovery production management tools that incorporate indexing, OCR, searches, and what not.
For more complicated stuff you can use vendors.
It sounds like your old firm liked to bill clients for all of that extra staff time -- keep the revenue up.
You have a $VeryExpensive accident.
There are $LargeNumber companies which have some partial liability.
That they are liable is extremely easy to prove, but the extent of the liability is extremely difficult and can be extremely costly on a per company bases.
You also have a database which holds most of the contributions of each of these companies, allowing you to build up a case for why each company has a certain percent of liability. While there is a team of lawyers and a team of programmers working on this case, the ability of lawyers to pull up simple enough data reduces the dependency of involving the programmers, and the lawyers having a basic understanding of SQL helps them both communicating with the programming team and when they have to explain things in front of the judge. Being able to query the data allows for the lawyers to better grasp which cases are the most worthwhile to pursue.
And for macros, sometimes you don't have a simple database, but you do have very standardized forms that are easy to scrape data off of.
You have a set of documents you prepare regularly. Could be a Power of Attorney, a diversion agreement, whatever. You can highlight the frequently changed part and substitute information by hand... or you can set up a macro with a form to enter the information and have it automatically generate.
Attorneys are knowledge workers burdened with a lot of administrative nonsense. There is a lot of low hanging fruit for automation.
Law firms have been using software to do this for 2 decades. Rather than using macros, they have dedicated document-management systems that can generate templates/documents based on the type of filing, client, etc. that get further customized by lawyers as needed.
Another example, though a bit more general, would be an attorney trying to find documents in a case that were created around a certain date. An attorney without basic skills is, again, going to end up in a manual or semi-manual (with a basic tool) process. An attorney with basic programming skills is likely able to directly craft a query that produces the documents.
It doesn't make much sense for a $400/hr attorney to play around with scripts and such or otherwise do much of anything with document production (that is what staff is for).
If an attorney knows coding from a previous career, it can be helpful in a few cases, but for a non-technical attorney to try to pick up enough coding to do anything useful is a stretch.
A shell script to achieve your ends could be endlessly helpful here.
It is one thing to teach a non-techie lawyer how to "hello world" But getting them to understand file system attributes, permission schemes, file I/O, regular expressions, and so on, is where "learn to code" falls apart in this context.
Just getting a non-technical person to learn how to navigate in Powershell is a near impossibility.
This is not true at all. Salaries for starting lawyers at "BigLaw" firms are generally fixed...but only by firm and by location. So Firm A in NYC pays $XXXk but their LA office only pays $YYYk. Firm B probably pays close to $XXXk in NYC but might pay $ZZZk. And if you go down to the smaller firms, they could pay anywhere from $40k to $XXXk based on location, type of law, etc.
After the first year, very few firms are lockstep with regards to raises...in the past few years, I think only 1 or 2 major firms is still on the lockstep model. Raises after 2nd year are almost universally based on performance, which depends heavily on technical skill (technical meaning legal, not programming, skills).
It seems -to-edit many more than one or two of this hundred https://www.vault.com/best-companies-to-work-for/law/top-100... are still paying lockstep.
Cravath still lists lockstep raises for years 1-7. Skadden years 1-8. Latham 1-9. Davis Polk 1-6. Etc. Are the firms reporting one thing but actually doing something else?
They rest don't do lockstep anymore. On paper they start with lockstep, but actual raises are based on performance, location, legal group, etc. I have enough friends at Skadden and Latham in different offices to confirm that.
Though, an exception would be patent attorneys. Patent attorneys with CS/EE degrees are usually in high demand.
I say this because the bulk of work for many types of legal practice is information filtering/search/organization/and presentation, both in wrangling evidence and in exploring the law itself. Basic programming knowledge can do great magic in terms of making these processes more efficient, such as by programmatically manipulating the hundreds or millions of files that can be produced in legal cases.
In terms of more in-depth knowledge of programming, there is a definite place for it in the law (it has worked to my benefit), but I think that role is specialized/limited. I think improved software tools will, generally, fill the profession's need rather than every attorney attempting to specialize in another field enough to roll their own apps.