Lawyers vs. Programmers
Jul. 26th, 2004 04:14 pmThere's a joke I heard in the SCA:
The SCA runs the way it does because its laws are written by computer programmers. The USA runs the way it does because its computer programs are written by lawyers.
Which is not strictly true, but lawyers have a huge impact in how we do things, from every decision made to avoid a potential lawsuit, to the increasing complexity and obscurity of laws, to the one-winner one-loser assumption in all political contests. It's become so pervasive that some people get law degrees without ever intended to practice law, just so they can function in their preferred profession. Now there's a change in society--lots of people are learning programming as part of their jobs and former programmers are carrying their skills on to new careers. Jeff Jarvis thinks this will push us toward a more transparent system instead of the deliberate obscurity lawyers like to produce to protect their guild. Another blogger points out that while lawyers want to maintain the status quo programmers are producing constant change.
I'm more interested in another difference between the professions. To lawyers "truth" is ultimately what an individual or group says it is--a judge, a committee, Congress, the Supreme Court. That's who has the last word, and everyone has to live with it. Programmers--and other kinds of engineers--test their theories against the real world. If it works, great. If it doesn't, no appeals to any court or amendment to a law will fix it--you have to change the design/theory/approach. I think our society would be a lot healthier if we routinely tested ideas against Reality instead of Authority.
The SCA runs the way it does because its laws are written by computer programmers. The USA runs the way it does because its computer programs are written by lawyers.
Which is not strictly true, but lawyers have a huge impact in how we do things, from every decision made to avoid a potential lawsuit, to the increasing complexity and obscurity of laws, to the one-winner one-loser assumption in all political contests. It's become so pervasive that some people get law degrees without ever intended to practice law, just so they can function in their preferred profession. Now there's a change in society--lots of people are learning programming as part of their jobs and former programmers are carrying their skills on to new careers. Jeff Jarvis thinks this will push us toward a more transparent system instead of the deliberate obscurity lawyers like to produce to protect their guild. Another blogger points out that while lawyers want to maintain the status quo programmers are producing constant change.
I'm more interested in another difference between the professions. To lawyers "truth" is ultimately what an individual or group says it is--a judge, a committee, Congress, the Supreme Court. That's who has the last word, and everyone has to live with it. Programmers--and other kinds of engineers--test their theories against the real world. If it works, great. If it doesn't, no appeals to any court or amendment to a law will fix it--you have to change the design/theory/approach. I think our society would be a lot healthier if we routinely tested ideas against Reality instead of Authority.
no subject
Date: 2004-07-26 02:42 pm (UTC)no subject
Date: 2004-07-26 02:49 pm (UTC)no subject
Date: 2004-07-26 03:28 pm (UTC)Hmmm--software shops have full-time testing people trying to find ways to figure out if the code is working right. I wonder if we'll ever have a Texas Department of Testing and Measurement doing research to figure out how well each of those expensive government programs works. Or if funding could be found to support something like that as an NGO. That'd be an interesting job. The hard part would be trying to get professionals who don't already have a vested interest in the outcome of each evaluation.
Lawyers
Date: 2004-07-27 09:19 am (UTC)Case law is less analogous to computer code than it is to the procedural hacks users work out. Import the report text to a spreadsheet and massage, export the results to a delimited flat file, import THAT to a data-base wizard to assign keys and break into 4 related tables, update one table to a keyed standard table, (rejecting any duplicated records) in order to pick up recent changes ... In an ideal world the procedure could be coded (a macro?) to react to the incoming text by updating the records. In practice, it's a lucky office that has such procedures written down and not passed from departing user to incoming replacement user via folklore, oral tradition, and one-time on-the-job-training.
SCA is getting lawyer-y
Date: 2004-07-27 09:57 am (UTC)http://www.sca.org/BOD/announcements/commentary.html?id=12
no subject
Date: 2004-07-28 07:29 pm (UTC)no subject
Date: 2004-07-29 07:05 am (UTC)